-
Notifications
You must be signed in to change notification settings - Fork 39
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
Don't read /proc/$PID/maps for core files #12
Comments
Do you have a PR? |
Not yet, I just added a "return" to the top temporarily to work on the core file I'm looking at. I can do one later after I've had a chance to look at the gdb API which I haven't used before (unless you fix it first) |
If we return immediately, it presumably won't find the mmapped chunks. I'm told that
works for core files from NT_FILE; this could be a way to find them when running on a coredump. |
Same problem hiere:
|
There is another util for analyzing heap in core dumps: https://github.com/vmware/chap |
iter_mmap_heap_chunks() tries to read /proc/$PID/maps which only works if the process is currently running. If you are using a core file, it will fail with an exceptions.IOError.
Having iter_mmap_chunks() return immediately if we are processing a core file rather than having an attached process solves it.
The text was updated successfully, but these errors were encountered: