-
Notifications
You must be signed in to change notification settings - Fork 847
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
maximum recursion depth exceeded - gdb -c core_dump #985
Comments
Can you provide a minimal working example of this so I can fix it once and for all? |
this is the core dump |
Thanks, I can reproduce this and I get some workaround which isn't perfect yet but it can be found here in case u want to use it now: https://github.com/disconnect3d/pwndbg/tree/workaround-985 Due how it is made Pwndbg does not resolve proper vmmap, so e.g. legend does not work well. I guess we could maybe parse |
Yes, it works better now.
Thanks.
Le ven. 26 nov. 2021 à 19:37, Disconnect3d ***@***.***> a
écrit :
… Thanks, I can reproduce this and I get some workaround which isn't perfect
yet but it can be found here in case u want to use it now:
https://github.com/disconnect3d/pwndbg/tree/workaround-985
Due how it is made Pwndbg does not resolve proper vmmap, so e.g. legend
does not work well. I guess we could maybe parse info proc mapping
instead of all the thing we do now or we did in the past to grab those
pages in this particular case...
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#985 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANURVASCBV42BWBRUTQENW3UN7HV7ANCNFSM5I22TMJQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
This commit fixes our headaches with core files debugging. The TL;DR is that we will now try to parse `info proc mappings` and `maintenance info sections` to give users best possible UX/vmmaps information. Related: * https://sourceware.org/bugzilla/show_bug.cgi?id=29508 * #985 * #954
* Fix coredump debugging This commit fixes our headaches with core files debugging. The TL;DR is that we will now try to parse `info proc mappings` and `maintenance info sections` to give users best possible UX/vmmaps information. Related: * https://sourceware.org/bugzilla/show_bug.cgi?id=29508 * #985 * #954 * cleanup * cleanup * Fix core dbg when EHDR map is not mapped
This has been fixed in #1079 The returned vmmap information is not ideal, but that's more or less what we get right away from GDB. (We may be able to improve this by using readelf on the core file, but it would not be so generic solution/may not work in all cases etc. so I am still not sure about using it) |
core.4408.zip
Description
We have this error when we analyse a core dump generated after segmentation fault due to the buffer overflow :
Exception occurred: Error: maximum recursion depth exceeded while calling a Python object (<class 'RecursionError'>).
We launch gdb and thus pwndbg with this option : -c
Steps to reproduce
My setup
ubuntu bionic64 on vagrant and virtualbox
python version : any
gdb version : 8.1.1-0ubuntu1
The text was updated successfully, but these errors were encountered: