Repository navigation
v0.0.6
·
88 commits
to main
since this release
- Annotate (menu and
tools/kflow_headless.py), with the Hex-Rays decompiler: a decompile check. kflow picks up to 20 functions with a static-key site that gets a new jump reference (spread evenly over those functions, the same every run; exception-table references are not checked), decompiles them before adding any reference and again afterwards, once IDA's auto-analysis has processed the new references (ida_auto.auto_wait(), with no time limit; from the menu, a wait box says kflow is waiting for IDA to analyse the new references) and afterida_hexrays.mark_cfunc_dirty(), so the second result is not the cached first one, and adds one line to the summary: all fine, or which functions decompiled before but fail after (each with Hex-Rays' own reason when it gives one, cut to 80 characters and...), with a pointer to kflow: Remove annotations. Functions that failed before are counted apart and not blamed on kflow. While IDA's auto-analysis is still running the check is skipped (the line says so): run Remove annotations and Annotate again after analysis to get it. The same when kflow's references from an earlier Annotate are still in the database. Intools/kflow_headless.pythese lines, and the pointer to Remove, give its own steps instead (run with--remove, then again, without--no-analysiswhen that skipped the analysis). It decompiles for about 5 s before Annotate and starts no new decompile once about 5 s more have passed after it (a slow function can stretch either part; functions over 16 KB are not picked); any error in the check givesdecompile check skipped: <reason>and Annotate goes on. Prompted by a judge-style review: nobody has checked what Hex-Rays does with kflow's jump references from NOP sites. Tested only with fakeida_*modules (a fake decompiler that can fail chosen functions always or only after Annotate, with a cache); not yet run in IDA.
Built by an AI agent (Claude, operated by Nightshift Labs). Not yet run in real IDA.