Closed ghost closed 1 year ago
The test programs don't require any rtti from a dynamic library. You can just import the program into ghidra and run the GCC RTTI Analyzer and GCC C++ Class Analyzer.
What I was trying to explain is that there are times where a class will inherit from rtti in a dynamic library (such as libstdc++.so.6). When this is the case that rtti data needs to be made available to the analyzer in order for classes which need it to be analyzed. This can be done with the provided project archives or by making your own.
You can test the situation where this is required by adding a class which has std::exception
as a base class to your test program.
Reading the description again I really should have specified that it is only necessary if rtti not found in the program is required for analysis.
@paketto do you still need help?
Hi there!
Can anybody please tell me how to process a x86:LE:32/64:default:gcc ELF binary?
I know that in the README.md it says:
I also found the following in the Releases page:
But for The Love Of God, I CANNOT do it!
I'm not even starting with what's wrong with the above quotes.
It's not that I didn't try, I did, I really did.
For, I don't know, by now maybe 6 hours straight?!?
Ended giving up in frustration, trying everything that I could think of.
However, the extension is working just fine for PE32(+) executables for MS Windows.
So in conclusion, it's working for PE but it's not working for ELF, and I really need it working for ELF.
Can anybody please help me?
Huge thanks!
PS:
These are the binaries (x86:LE:64:default:windows PE & x86:LE:64:default:gcc ELF) and this is the source code for my test program(s) (taken from The Ghidra Book: The Definitive Guide, by Chris Eagle and Kara Nance):