diff options
| author | James Hunt <james.hunt@ubuntu.com> | 2015-02-05 14:23:17 +0100 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2015-02-21 08:32:11 +0100 |
| commit | 674f11ecbc25eb616b596b2920385d160d94bbf1 (patch) | |
| tree | 911a9599c1acfa68062dca0bf3df53d4e72704be | |
| parent | ca126346813b3fc06925958bdefa597ff5ef693b (diff) | |
| download | man-pages-674f11ecbc25eb616b596b2920385d160d94bbf1.tar.gz | |
ptrace.2: Explain behaviour should ptrace tracer call execve(2)
This behaviour was verified by reading the kernel source and
confirming the behaviour using a test program.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
| -rw-r--r-- | man2/ptrace.2 | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/man2/ptrace.2 b/man2/ptrace.2 index 2c676e3a21..0365698bde 100644 --- a/man2/ptrace.2 +++ b/man2/ptrace.2 @@ -1974,6 +1974,9 @@ In Linux kernels before 2.6.26, .BR init (1), the process with PID 1, may not be traced. .LP +A tracees parent continues to be the tracer even if that tracer calls +.BR execve (2). +.LP The layout of the contents of memory and the USER area are quite operating-system- and architecture-specific. The offset supplied, and the data returned, |