> It's definitely a bug in strace. For some reason (I don't care about) > the execve() syscall produces an extra notification. However, this > notification message is suppressed when SIGTRAP is blocked. This > explains why the test case fails only when SIGTRAP is blocked. What do you mean by "extra"? There is a SIGTRAP sent after execve completes when ptraced, even when PTRACE_SYSCALL is not being used. So for an execve that succeeds under PTRACE_SYSCALL, there is a ptrace_notify at syscall entry, then a SIGTRAP queued (i.e., not seen by ptrace if blocked), then a ptrace_notify at syscall exit. If that's what's happening (including the blocked SIGTRAP not being seen by the ptracer, i.e. strace), then there is no mystery (and no bug). Thanks, Roland -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|