forked from cmu-sei/kaiju
-
Notifications
You must be signed in to change notification settings - Fork 22
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 'Analyzing gaps' for a suspiciously long time. #81
Labels
bug
Something isn't working
Comments
Thanks for reporting. This definitely sounds like a bug to me. Did this happen to be for the same executable that you already shared with me? |
Yes, it's the same! |
Without disassembly improvements:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Ghidra (11.2.*) spends a suspiciously long time at the 'Analyzing gaps' step when analysing a 9 MB 32 bit windows executable (the same executable from cmu-sei/pharos#274). At first I didn't want to report this as a bug because "surely it just takes this long" until I saw a similar issue (#65) where someone was analysing a larger executable for 9 hours and after a fix it end up being 640 seconds so I assume something has to be wrong here as well and it shouldn't take this long.
Looking at the logs (of which I have 2 GBs of (spread across 29 files) just from this!) it's mostly
Skipping address
, searching for any of the addresses shows around 67 matches/file. Looking for anything notSkipping address
isCreated alignment at:
, the addresses are unique but in between them there is this repeating:Always the same address.
There is nothing else in the log files (other than when I stopped it),
Kaiju Disassembly Improvements
ran for 14 hours and did 26880 iterations.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Less waiting? (Unless this isn't a bug and is expected behaviour...)
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: