662548c826
Instead of maintaining separate swig interface files, we can use the API headers directly. They implement the exact same C++ APIs and we can conditionally include the python extensions as needed. To remove the swig extensions from the API headers when building the LLDB framework, we can use the unifdef tool when it is available. Otherwise we just copy them as-is. Differential Revision: https://reviews.llvm.org/D142926
15 lines
567 B
OpenEdge ABL
15 lines
567 B
OpenEdge ABL
%feature("docstring",
|
|
"Represents a list of machine instructions. SBFunction and SBSymbol have
|
|
GetInstructions() methods which return SBInstructionList instances.
|
|
|
|
SBInstructionList supports instruction (:py:class:`SBInstruction` instance) iteration.
|
|
For example (see also :py:class:`SBDebugger` for a more complete example), ::
|
|
|
|
def disassemble_instructions (insts):
|
|
for i in insts:
|
|
print i
|
|
|
|
defines a function which takes an SBInstructionList instance and prints out
|
|
the machine instructions in assembly format."
|
|
) lldb::SBInstructionList;
|