Open mucoze opened 3 days ago
There are many many ways a file could be in a non-compliant form and we cannot check for all cases. If you attach a sample file I can take a look at handling the case better. I can certainly handle the null case identified by the stack trace above, although I would like to understand how such a binary would handle its dynamic relocations properly.
@mucoze Could you please attach a file which exhibits this behavior. I have been unable to reproduce.
@ghidra1 Hi, I have crafted a sample binary that you can use to reproduce the error.
In the zip archive, you can find the one with corrupted Section Header Table and also the original file. sample_library.zip
Ghidra importing fails when the binary has a corrupted section header table.
The sample is
ARM:LE:32:v8:default
Error output:
readelf output
Expected behavior If possible, Ghidra can force import of binaries that have a corrupted section header table. Otherwise, it may just refuse to import with a warning, instead of being fail.
Screenshots
Environment: