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>

diff --git a/man2/ptrace.2 b/man2/ptrace.2
index 2c676e3a21b95dadeaa598aac4fe57bc89da3c30..0365698bde2bc2f1692f797c1a6e21e633e42d48 100644 (file)
--- 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,