summaryrefslogtreecommitdiffstats
ModeNameSize
-rw-r--r--.gitignore245logstatsplainblame
-rw-r--r--README.md11221logstatsplainblame
-rw-r--r--TODO2857logstatsplainblame
d---------docs297logstatsplain
d---------experiments529logstatsplain
-rwxr-xr-xida-tui913logstatsplainblame
d---------idatui934logstatsplain
-rw-r--r--logo-trans.png1740746logstatsplainblame
-rw-r--r--logo.ans40439logstatsplainblame
-rw-r--r--logo.png818833logstatsplainblame
-rw-r--r--pyproject.toml814logstatsplainblame
d---------server43logstatsplain
d---------tests819logstatsplain
d---------tools87logstatsplain
-rw-r--r--uv.lock11747logstatsplainblame

object 2c53aeb16bca2fef04af1df2023ac0fd41e12bc3 type commit tag pre-codemode tagger blasty peter@haxx.in 1786108456 +0200

Last state of the private idalib worker backend

The backend ida-tui used before the IDA Code Mode port: idatui/worker.py + worker_client.py (a private subprocess speaking length-prefixed pickle over a unix socket) with server/patch_server.py injecting our extra tools into ida-pro-mcp.

Kept as the A/B reference. The port replaces the transport wholesale, so this is the tag to check out when asking 'is this a regression or has it always done that?' -- which is exactly how the xref ordering, the trace-follow race and several performance claims were settled. tests/run.py works here, and /tmp/cmport/bench.py (if still around) picks whichever client the checked-out tree has, so it benchmarks this tag unmodified.

Reference numbers on targets/echo, this box: heads(200 rows) 2.65ms, decompile warm 30.0ms, decomp_map 45.8ms, full pilot suite ~60s.