Rather than loading the raw approximate decompile code into SQLite, you'll likely get better results using Ghidra directly with tool calls through an MCP adapter. This is especially important when the analysis tracing fails, like with some complex indirect jump patterns with vtables. Xrefs and pattern searches are of course natively supported, and you can load in memory snapshots.
A simple "/goal analyze this codebase, assign names for each function, and creates named structs for parameters." works well, even with quite weak agents. Remember, parsing through heaps of text is their forte!
This setup also works for more exotic non-x86 architectures with more dynamic code loading, like PS2, N64, etc.
A simple "/goal analyze this codebase, assign names for each function, and creates named structs for parameters." works well, even with quite weak agents. Remember, parsing through heaps of text is their forte!
This setup also works for more exotic non-x86 architectures with more dynamic code loading, like PS2, N64, etc.