PyDA
PyDA copied to clipboard
jchristman
Python binary DisAssembler
All data sections should be represented as code in a manner similar to that used by IDA. As an initial step, single-byte declarations are good enough. For example, for the...
https://www.hex-rays.com/products/ida/tech/flirt/in_depth.shtml
Currently, x86 is the only arch with identified function prologues/epilogues. Edit asmfeatures.py appropriately.
Should implement a logger because multiprocessing cannot access print in many cases. This will allow us to get information from the other processes.
For example, each section could have a "range" object with flags for ranges. As an inefficient example: type_ranges = [["0x8040000:0x8040100", "data"], ["0x8040101:0x8040243", "text"], ...] Similar to #16
Give the ability to mark highlighted instructions as data/code.
So far we've only consistently tested x86. Do more. https://github.com/JonathanSalwan/binary-samples
It's a little to tightly coupled and I'd like for us to move that code out of the maininterface.py if possible.
Instead of multithreading everything, investigate changing the threadpoolexecutor to possibly use multiprocessing to take advantage of multiple cores.