-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
x86 binary loops r2 #520
Comments
"built from git yesterday at commit 34e2473" |
Left |
In fact the fatmach0 binary is not loaded properly. text section looks filled by zeroes. Loading the extracted x86-32 binary with rabin2 -x works fine here. |
To be clear, r2 loads the binary when you use the -A flag? How long does it take to complete the analysis? It could be my environment, which is RHEL6. |
That’s a big binary, the analysis can take a lot of time. With the wrong IO the analysis is completely wrong too. Just press ^C If you use -A it will analyze the whole binary at start, that’s fine. On 09 Jan 2014, at 01:54, roysjosh notifications@github.com wrote:
|
Well, I suppose that's the question of this ticket: should -A lead to a seemingly endless loop? I left r2 running over night, and almost 20 hours later it had consumed ~12GB of RAM and was still going on the analysis. |
Oh, my semi-metric was that the ppc binary analysis completed within an hour or two. |
This binary is huge. but surely 20h of analysis is pretty bad news. There maybe a bug in the analysis, but bear in mind that the x86 code analysis is more complex and complete than the arm one. also, there are several points to optimize this. The thing is that there shuold be no endless loops in the analysis. If there’s one it shuold be reproducible in a smaller binary. On 09 Jan 2014, at 02:00, roysjosh notifications@github.com wrote:
|
There have been several analysis optimizations which should make the analysis faster and take much less memory. I have also fixed some mach0 issues, but not all of them, and the binary is not yet loaded properly. There are several other optimizations planned, and hopefully I'll have some time to review that mach0 issue soon |
|
Fatmachos are broken . See @deeso
|
Fixed here: 1fbc7f2. Try now. |
I'm still learning r2, but analysis has definitely gotten faster and memory use seems to be more stable. Thanks. |
fatmach0s should be working again now. On 28 Apr 2014, at 09:01, Sergi Alvarez pancake@nopcode.org wrote:
|
The i386 binary out of the MachO "fat" binary at http://energylab.hpa.edu/public/vr/vr-archive/programs/EyeTV.app/Contents/MacOS/EyeTV loops
r2 -A x86
where x86 is the extracted binary fromrabin2 -x EyeTV
renamed from EyeTV.fat/EyeTV.x86_32.1 to x86.The text was updated successfully, but these errors were encountered: