Zhihui Zhang <[EMAIL PROTECTED]> writes: > - PT_CONTINUE + waitpid() works fine, the trace program prints out values.
This is expected behaviour. > - PT_CONTINUE alone does not work but no core-dump caused by SIGTRAP > - PT_DETACH + waitpid() does not work and core-dump > - PT_DETACH alone does not work and core-dump. These three cases are unexpected. I'll have to dig some more into this, but I'm afraid I won't have time until some time next week. > Who is sending the SIGRAP (5) signal? execve(2) in kern_exec.c posts SIGTRAP if the process has debugging turned on (which it does as a result of PT_TRACE_ME). DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
