1441ffe6a6
Update examples and docs to demonstrate using `__lldb_init_module` instead of
the idiom that checks for `lldb.debugger` at the top-level.
```
if __name__ == '__main__':
...
elif lldb.debugger:
...
```
Is replaced with:
```
if __name__ == '__main__':
...
def __lldb_init_module(debugger, internal_dict):
...
```
This change is for two reasons. First, it's generally encouraged not to only
use the convenience singletons (`lldb.{debugger,process,target,etc}`)
interactively from the `script` command. Second, there's a bug where
registering a python class as a command (using `command script add -c ...`),
result in the command not being runnable. Note that registering function-backed
commands does not have this bug.
Differential Revision: https://reviews.llvm.org/D117237
28 lines
1.1 KiB
Python
Executable file
28 lines
1.1 KiB
Python
Executable file
import lldb
|
|
|
|
|
|
def disassemble(debugger, command, result, dict):
|
|
if lldb.frame.function:
|
|
instructions = lldb.frame.function.instructions
|
|
start_addr = lldb.frame.function.addr.load_addr
|
|
name = lldb.frame.function.name
|
|
elif lldb.frame.symbol:
|
|
instructions = lldb.frame.symbol.instructions
|
|
start_addr = lldb.frame.symbol.addr.load_addr
|
|
name = lldb.frame.symbol.name
|
|
|
|
for inst in instructions:
|
|
inst_addr = inst.addr.load_addr
|
|
inst_offset = inst_addr - start_addr
|
|
comment = inst.comment
|
|
if comment:
|
|
print("<%s + %-4u> 0x%x %8s %s ; %s" % (name, inst_offset, inst_addr, inst.mnemonic, inst.operands, comment))
|
|
else:
|
|
print("<%s + %-4u> 0x%x %8s %s" % (name, inst_offset, inst_addr, inst.mnemonic, inst.operands))
|
|
|
|
# Install the command when the module gets imported
|
|
def __lldb_init_module(debugger, internal_dict):
|
|
debugger.HandleCommand(
|
|
'command script add -f gdb_disassemble.disassemble gdb-disassemble')
|
|
print('Installed "gdb-disassemble" command for disassembly')
|