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

Andreas Schwab schwab at redhat.com
Fri Mar 5 09:30:04 UTC 2010

Roland McGrath <roland at redhat.com> writes:

> If you trace an execve, you're going to get its syscall exit stop
> before you get its old-style traced-exec SIGTRAP.

No, you don't.

> But, for exec doesn't it make sense to call it a possible ptrace stop only

What if PTRACE_O_TRACEEXEC doesn't work?  That contradicts your own


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