-
Notifications
You must be signed in to change notification settings - Fork 184
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
Comments
We are investigating a concurrency problem in #267. Can you try to run without |
Yes, I'm on it! Will update. |
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 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! |
Great. Sounds like pretty normal warnings.
…________________________________________
From: Matvei ***@***.***>
Sent: Wednesday, April 24, 2024 1:53 PM
To: cmu-sei/pharos
Cc: Edward J Schwartz; Assign
Subject: Re: [cmu-sei/pharos] Segmentation fault (core dumped) (Issue #268)
Warning: External Sender - do not click links or open attachments unless you recognize the sender and know the content is safe.
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
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!
—
Reply to this email directly, view it on GitHub<#268 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AL6ZAVCX5ERZZWKEK72XYFDY67WR5AVCNFSM6AAAAABGXKBD66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZVGUYTMOBTHE>.
You are receiving this because you were assigned.Message ID: ***@***.***>
|
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. |
That functionality was moved to https://github.com/certcc/kaiju Thanks for telling us about the broken link, we'll get that fixed. |
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:
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 :)
The text was updated successfully, but these errors were encountered: