-
Notifications
You must be signed in to change notification settings - Fork 953
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 in llvmir2hll due to insufficient stack space #47
Comments
@Convery , how to debug it? |
Thank you for the report. Segmentation faults in these phases ( At the moment, the following workarounds are available:
For a proper fix, a rewrite of the phases will be needed (recursion -> iteration). |
@s3rvac , I've increased the stack size in two times (up to 32GB) and rebuilt the binary but that didn't help:
Do you think I need to double it again? |
@jazzl0ver I am afraid that further increasing will not help that much. We will have to investigate this. The binary file is probably incorrectly decoded. |
@s3rvac , thank you for your help! Hope, you'll be able to fix it quickly |
I'd just like to add that this problem can happen in other phases too:
Unfortunately I can't share the executable, not sure if I can mention it. |
hi. just tried the latest sources and the issue is still there:
Any chances you gonna fix that soon? |
@jazzl0ver This will take some time. It is not the kind of problem that you fix with a small modification. I'm already working on a new decoder in branch |
@PeterMatula , I appreciate your quick reply, thank you! |
Hi. Just curious if you have any progress on this |
In general, the new decoder helped. But there is huge amount of data in text section in this sample, and we are still not as good as we should. Also, when I was working on a new decoder, I came across samples that were decoded perfectly (no data interpreted as code), they were not even that complex, and they still spent huge amount of time in |
Thank you, @PeterMatula ! I'll give it a try and let you know |
@PeterMatula , now it looks different:
Same errors when issued with the extra option you mentioned:
BTW, if you were able to de-compile my file, could you please send me the sources? |
--max-memory always defaults to half of your physical memory now, which is exactly what's happening here. You should probably use --max-memory 60000000000 or so. |
Thanks, @silverbacknet . Unfortunately, that didn't help:
Do you think I need more RAM? |
I think you will simply not decompile this file using RetDec at the moment. And even if you would, the result would not be very good. We need to make it better in order to handle something like this in a reasonable time and quality. |
I see :( Hope you will continue improving it. |
@megacoderencoderdecoder Because you spam our issue tracker and annoy people by unnecessarily tagging them. |
Hi. Running retdec under Windows Server 2016, getting this:
myfile.exe can be downloaded here: https://www.dropbox.com/s/jm7xnxtto3r4jxf/myfile.zip?dl=0
Please, help!
The text was updated successfully, but these errors were encountered: