Skip to content
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

Segmentation fault (core dumped) #268

Closed
sudoLife opened this issue Apr 24, 2024 · 6 comments
Closed

Segmentation fault (core dumped) #268

sudoLife opened this issue Apr 24, 2024 · 6 comments

Comments

@sudoLife
Copy link

Hi,

First, thank you for all your work!

I am trying out OOAnalyzer on a 5.6M 32-bit DLL using the guide for large executables. I get a segfault on step 2 when trying to use the actual OOAnalyzer.

My computer specs:

Linux Distribution:             Arch Linux
Linux Kernel:                   6.6.26-1-lts
Computer Model:                 TUXEDO TUXEDO Pulse 15 Gen1 Standard
Processor (CPU):                AMD Ryzen 7 4800H with Radeon Graphics
CPU Sockets/Cores/Threads:      1/8/16
Architecture:                   x86_64 (64-bit)
Total memory (RAM):             63720 MiB (63GiB) (66816 MB (67GB))

I tried using 128000, 57000 and 50000 memory parameter with 16, 16, and 4 threads, respectively, with the same result. I don't know if I am missing some calculation here. Maybe it was never meant to be used on DLLs?

If you want me to debug this somehow, give me some pointers and I'll try my best :)

@sei-eschwartz
Copy link
Collaborator

We are investigating a concurrency problem in #267. Can you try to run without --threads=X and see if the crash occurs?

@sudoLife
Copy link
Author

We are investigating a concurrency problem in #267. Can you try to run without --threads=X and see if the crash occurs?

Yes, I'm on it! Will update.

@sudoLife
Copy link
Author

sudoLife commented Apr 24, 2024

UPD: It's gotten to function analysis which it couldn't do before! Currently at 3%. I set memory to 57000. It has some errors like "analysis of function <address> failed: relative memory exceeded" and things like that but I assume that's just part of the process since it doesn't crash.

I'll let you know if it gets to the end and thanks for such a prompt response!

UPD 2: got to the end of step 2!

@sei-eschwartz
Copy link
Collaborator

sei-eschwartz commented Apr 24, 2024 via email

@sudoLife
Copy link
Author

Thanks, it finished! I guess we can close this issue, and I'll keep watch over the related bug.

Quick question, where is the readme for putting the results to Ghidra? This link from this README section is broken.

@sei-eschwartz
Copy link
Collaborator

That functionality was moved to https://github.com/certcc/kaiju

Thanks for telling us about the broken link, we'll get that fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants