Closed vanhauser-thc closed 3 years ago
This happens if either the feature "GCC C++ Class Analyzer (Prototype)" or "GCC RTTI Analyzer (Prototype)" are activated. Are they include and active by default? or is that a plugin I installed and blindly forward copied to the new ghidra version?
or is that a plugin I installed and blindly forward copied to the new ghidra version?
This is likely the issue. There should be no java.lang.NoSuchMethodError
s happening in a build of Ghidra. The old plugin is calling a method that has been changed or removed. If you have the source for the plugin, you should be able to load it into the dev environment and see the compile issues.
Describe the bug When auto analyzing an aarch64 linux binary I receive an exception for demangling and the process aborts. Issue seems to be a bug in identifying the type of a mangled object.
To Reproduce
Expected behavior Auto Analysis runs though without issues.
Screenshots
Attachments I cannot reveal the program where this happens ... :(
Environment (please complete the following information): Build Date: 2020-Dec-29 1701 EST Ghidra Version: 9.2.2 Java Home: /usr/lib/jvm/java-11-openjdk-amd64 JVM Version: Debian 11.0.10-ea OS: Linux 5.9.0-kali5-amd64 amd64 Workstation: localhost