-
Notifications
You must be signed in to change notification settings - Fork 239
Unexpected ptrace(2) exception: Failed to PTRACE_PEEKDATA: Input/output error #129
Comments
What is the address printed (i.e. the complete exception message, including the hex string at the end)? Also, can you provide me the output of |
Here's the output of
I rebuilt it to only drop the current sample if a PTraceException is thrown, which gave me these exceptions over the last hour or so:
|
looking at
|
The ones that say
That will help figure out where in the code the error is happening. Also -- are you profiling a regular Python 2.7 process, or some kind of embedded Python build (e.g. a uwsgi worker process)? |
This is a regular Python 2.7.6 process. Here's the backtrace:
|
I've also gotten this issue profiling a django uwsgi app: Sometimes happens after a few seconds of clicking around, sometimes doesn't happen for a while, my current workaround is to profile in smaller bursts |
@stevenkaras That is interesting because that shows pointers well beyond where I would expect the stack to end. This differs from system to system, but here's what I see locally:
So on my system in this particular run the stack was in the range 7ffd515b8000-7ffd515d9000 which is typical (the exact numbers can vary). Normally it is some number like 0x7ff and then other digits after that, but before 0x7ffff... You're seeing a stack entry well beyond that, i.e. from your trace:
That address is 7728 bytes before where I expect userspace memory to end (0x7fffffffffff). Would need more data from gdb to debug further. @bk-equityzen I would be interested to see what the memory map looks like in that situation as it appears not to be at the top of user memory. You can use /proc/PID/maps from the process as I did here to look at that. |
I have the same errors on Ubuntu 18.10 |
I'm encountering this error after about 15 minutes of tracing a running python process.
Ubuntu 14.04, running 4.4.0-75-generic, tracing a long-lived python 2.7.6 process, built from source (e9c6b7a).
The text was updated successfully, but these errors were encountered: