-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stuck at "Processing PLT/GOT" when importing a MIPS ELF executable on Ghidra for Windows #1086
Comments
The are many variations of MIPS ELF binaries for us to guess at the cause. You have not provided sufficient information to identify the problem. Are you able to identify where in the Ghidra source it is hung up? While Ghidra is hung, you can try running the Java jstack command, from a command shell, giving the numeric PID of the Ghidra process which can be identified using the Java jps command. Copy the full stack trace to this issue. |
|
Could you try a binary import and run only the ELF Analyzer. Although this too could get hung up if it is miscalculating the symbol count. This should markup the ELF headers including the dynamic table section. Once imported goto the _DYNAMIC symbol and locate the entries which correspond to DT_MIPS_GOTSYM and DT_MIPS_LOCAL_GOTNO . Does it have dynamic entries for either DT_GNU_HASH or DT_HASH? Which? It is possible the hash table processing messed up and produced a very large symbol count. Also locate the entry DT_SYMTAB and navigate to its referenced location where you should see an array of symbol entries. How many entries in the array. It is likely that debug of the ELF import of your binary will be necessary to identify and resolve the issue you are experiencing. |
Could you please try the latest release 9.2. Some changes were made in this area which may have resolved this issue. |
Hello,
Ghidra gets stuck at "Processing PLT/GOT" and does not move to the next step. It happens when I try to import a MIPS executable. I use the Windows version.
The text was updated successfully, but these errors were encountered: