| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
llvm-svn: 132019
|
|
|
|
| |
llvm-svn: 132018
|
|
|
|
|
|
|
|
|
| |
the __init__
method definition before other method definitions. Instead, do without it and process
the class with IsValid() method definition in all possible states.
llvm-svn: 132016
|
|
|
|
| |
llvm-svn: 132002
|
|
|
|
|
|
|
|
|
|
|
| |
method definitions.
object.__nonzero__(self) is called to implement truth value testing and the built-in operation bool(),
via a simple delegation to self.IsValid().
Change tests under python_api/lldbutil to utilize this mechanism.
llvm-svn: 131494
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
unambiguous iteration support. So that we could, for example:
...
REGs = lldbutil.get_GPRs(frame)
print "Number of general purpose registers: %d" % len(REGs)
for reg in REGs:
print "%s => %s" %(reg.GetName(), reg.GetValue())
...
llvm-svn: 131418
|
|
|
|
|
|
| |
test case to take advantage of 'ths_module == that_module'.
llvm-svn: 130709
|
|
|
|
| |
llvm-svn: 130698
|
|
|
|
| |
llvm-svn: 130533
|
|
|
|
|
|
| |
restored after parsing "SBTarget". Indentation matters in Python. :-)
llvm-svn: 130532
|
|
|
|
|
|
|
| |
the breakpoint ID and provides the semantics needed for '==' and '!='. And
modify LLDBIteratorTestCase.lldb_iter_2() to use '==' between two SBBreakpoint's.
llvm-svn: 130531
|
|
|
|
| |
llvm-svn: 130461
|
|
Python module.
This is so that the objects which support the iteration protocol are immediately obvious
from looking at the lldb.py file.
SBTarget supports two types of iterations: module and breakpoint. For an SBTarget instance,
you will need to issue either:
for m in target.module_iter()
or
for b in target.breakpoint_iter()
For other single iteration protocol objects, just use, for example:
for thread in process:
ID = thread.GetThreadID()
for frame in thread:
frame.Disassemble()
....
llvm-svn: 130442
|