[PATCH] Try to use PTRACE_SETOPTIONS to handle non-ptrace SIGTRAP

Andreas Schwab schwab at redhat.com
Fri Jul 23 07:54:34 UTC 2010


Roland McGrath <roland at redhat.com> writes:

> Furthermore, the actual behavior of Linux kernels where TCB_WAITEXECVE
> is needed (i.e. PTRACE_O_TRACEEXEC not supported or not yet in force)
> is that a normal SIGTRAP signal is generated, so the normal ptrace
> signal stop for that comes only after the syscall-exit stop for the
> execve call completing.

This is irrelevant.  With the old code the flag is set in both cases
which is obviously wrong.

Andreas.

-- 
Andreas Schwab, schwab at redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84  5EC7 45C6 250E 6F00 984E
"And now for something completely different."




More information about the Strace-devel mailing list