174 lines
21 KiB
Markdown
174 lines
21 KiB
Markdown
# Reverse-engineering tool integrations
|
|
|
|
REA can call caller-supplied GNU objdump, GDB, and Rizin installations. REA does not install or update these tools. Static objdump/Rizin workflows use the same services from CLI and MCP. GDB's persistent MCP sessions and ephemeral CLI command are available only on Linux. Persistent debugger sessions exist only for the lifetime of the REA MCP server process.
|
|
|
|
In a shared MCP server, unrestricted Rizin and Cutter commands, GDB console
|
|
commands, Rizin debugger start/close, and GDB debugger close retire any active
|
|
binary analysis session after the operation. This prevents a fresh analysis
|
|
provider from being rebound automatically while command effects may still be
|
|
writing. After the command and any background writers have stopped, call
|
|
`open_binary` explicitly before continuing analysis. A successful command
|
|
response alone does not prove that background writers have stopped. An active
|
|
Ghidra analysis session must be closed explicitly before an external mutation
|
|
can run.
|
|
|
|
## GNU objdump
|
|
|
|
`inspect_with_objdump` and `rea inspect-with-objd |