is not in the normal signal delivery path. This means the parent
cannot do ptrace(PTRACE_CONT) with a signal or ptrace(PTRACE_KILL).
kill() with a SIGKILL signal can be used instead to kill the child
process after receiving one of these messages.
Paolo (Blaisorblade) Giarrusso, and Charles P. Wright;
after a suggestion from Heiko Carstens.
Document the following ptrace requests:
PTRACE_SETOPTIONS (2.4.6)
plus associated flags:
PTRACE_O_TRACESYSGOOD (2.4.6)
PTRACE_O_TRACEFORK (2.5.46)
PTRACE_O_TRACEVFORK (2.5.46)
PTRACE_O_TRACECLONE (2.5.46)
PTRACE_O_TRACEEXEC (2.5.46)
PTRACE_O_TRACEVFORKDONE (2.5.60)
PTRACE_O_TRACEEXIT (2.5.60)
PTRACE_SETSIGINFO (2.3.99-pre6)
PTRACE_GETSIGINFO (2.3.99-pre6)
PTRACE_GETEVENTMSG (2.5.46)
PTRACE_SYSEMU (since Linux 2.6.14)
PTRACE_SYSEMU_SINGLESTEP (since Linux 2.6.14)