Closed JP-E closed 9 months ago
The bug is caused from an error in the Ghidra analysis. In my case, it was an error detecting the default processor and can be fixed by setting language=XXX
e.g. language=x86:LE:32:default
when calling pyhidra.open_program
.
We made an update to Pyhidra so that it will produce a more helpful error message when this happens.
This should be fixed in the latest release.
I get the following error opening some programs (Mach-O files, and some Windows PE files). I've debugged the error and it appears to come from
project.importProgram(binary_path)
returning None in pyhidra/core.py:86.Code to reproduce:
Happy to share files that cause this error, but some of them are malware. The OS X binary
/usr/bin/find
also triggers this bug.Version info:
Using Ghidra release 10.2.2, Python 3.11, Arch Linux.