https://bugzilla.novell.com/show_bug.cgi?id=819383 https://bugzilla.novell.com/show_bug.cgi?id=819383#c7 Michael Matz <matz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |schwab@suse.com --- Comment #7 from Michael Matz <matz@suse.com> 2013-05-13 12:04:31 UTC --- In this very situation it really sounds like a kernel bug, but that ESRCH isn't handled also indicates a problem in pldd itself. From the ptrace manpage: The tracer cannot assume that the ptrace-stopped tracee exists. There are many scenarios when the tracee may die while stopped (such as SIGKILL). Therefore, the tracer must be prepared to handle an ESRCH error on any ptrace operation. Unfortunately, the same error is returned if the tracee exists but is not ptrace-stopped (for commands which require a stopped tracee), or if it is not traced by the process which issued the ptrace call. The tracer needs to keep track of the stopped/running state of the tracee, and interpret ESRCH as "tracee died unexpectedly" only if it knows that the tracee has been observed to enter ptrace-stop. Note the "on any ptrace operation", which in my book includes PTRACE_DETACH. So, while strange from the kernel in this situation (and that needs investigation), it is explicitely allowed to return ESRCH. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.