In the last couple months, I have replaced so many scripts with prompts like "use idac to perform class recovery, rename variables and functions, set prototypes, make and apply types to make the decompilation output look like the original source"
https://t.co/AxNTKpWjEE
One of the long-standing challenges in C++ RE has always been vtable REconstruction. AI now solves this, and you actually get richer context than you'd ever get from manual recovery.
Previously, HexRaysCodeXplorer plugin was born to ease that pain back in the day, but now I need to rethink how to make it truly effective in this new reality.
Conventionally, if you want to test if an LLM can find a bug where the root cause is a memcpy into a statically sized stack buffer, you would not put exactly that in the prompt as an example.