[PATCH] Try to use PTRACE_SETOPTIONS to handle non-ptrace SIGTRAP
roland at redhat.com
Mon Mar 8 23:01:49 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.
> > How did you come to that conclusion?
> Reality check.
Sorry, this answer is wholly inadequate.
A "reality check" consists of a comparison of one's expectations to the
external reality with which one must mesh. When you show some details of
how the program you are hacking itself behaves, that does not constitute a
check against external reality.
I wrote a small test program and posted it. In that simple test program,
it is pretty easy to understand what the external reality (the kernel) is
doing. That observed reality does not comport with your claims about your
own "reality check". That is, what we must guess you are claiming, since
you didn't actually say anything.
If my observations using that program don't match yours, or my analysis of
those observations is wrong, you have to actually say something about these
conflicts. If you can't even be bothered to compose a complete sentence
about the details of the kernel behavior we are talking about, you are not
making a credible effort to resolve the questions I raised in my review of
More information about the Strace-devel