-
-
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
Hang in aac #15004
Comments
Isn't this the same as #14782 ? |
But this problem still there even in the newest version~ |
Because my fix havent been merged yet
… On 11 Sep 2019, at 04:17, Huanran.Wang ***@***.***> wrote:
Isn't this the same as #14782 ?
But this problem still there even in the newest version~
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
its merged and fixed. enjoy :) now it takes ~8s in my laptop |
will be good to have a smaller binary to put in the testsuite |
@radare Actually this one is not fixed, I just tried on master, both |
Can you try setting anal.nonull=8 and run aa again and ser if it hangs? Also, using anal.verbose sometimes is helpful
… On 15 Sep 2019, at 12:58, Maijin ***@***.***> wrote:
Reopened #15004.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
same with the nonull. (interestingly and unrelated likely, stopping |
ooook i found the root cause oft he problem and it basically requires a full rewrite of the whole fcn storage because the rbtree implementation is unmaintainable and buggy. i did a workaround in a PR that should make this work. and in this binary it turns from infinite time to 1.8s, so it seems like its improving the analysis somehow. i plan to rewrite all that stuff during the 4.x releases |
I pushed a workaround to solve this issue in here: bb810cf just use r2 -e anal.norevisit=true maybe we should rename this to anal.visitonce, but well, its just a hack at the end, but this binary exposes some other issues in the analysis when the binary is obfuscated. so its a good testcase for improving the analysis. ill keep the issue open and try to fix more things in further releases |
Via @Zurich1994
Work environment
Expected behavior
Analysis goes on. (864K binary)
Actual behavior
Analysis stall.
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: