Skip to contentSkip to conversation

ptrace.2: Explain behaviour should ptrace tracer call execve

PATCH In review James Hunt 2 participants 2 messages Sep 13, 2012 – Feb 5, 2015 1 message not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore

James Hunt

author
#0 lore raw

PATCH 1/1 ptrace.2: Explain behaviour should ptrace tracer call execve

This behaviour was verified by reading the kernel source and confirming the behaviour using a test program.

Applies to latest git repo.

Kind regards,

James.
--
James Hunt
____________________________________
http://upstart.ubuntu.com/cookbook
http://upstart.ubuntu.com/cookbook/upstart_cookbook.pdf

Quoted 1 line

From 44d1bffe6dfbaeaae3e0bafb7ec626eb362f97e2 Mon Sep 17 00:00:00 2001

From: James Hunt <james.hunt-GeWIH/[email protected]>
Date: Thu, 13 Sep 2012 21:53:18 +0100
Subject: Explain behaviour should ptrace tracer call execve.

---
 man2/ptrace.2 |    3 +++
 1 file changed, 3 insertions(+)
man2/ptrace.2 +3 -0
index c45e569..d051358 100644
@@ -1660,6 +1660,9 @@ In Linux kernels before 2.6.26,
 .BR init (8),
 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,
Signature · 1 line
1.7.9.5

A message that is not in the archive (sent off-list or not yet received): 50524A33.2030600-GeWIH/[email protected]

#2 lore raw
Quoted 4 lines · James Hunt

This behaviour was verified by reading the kernel source and confirming the behaviour using a test program.

Applies to latest git repo.

Thanks, James. Applied.

Cheers,

Michael

---
 man2/ptrace.2 |    3 +++
 1 file changed, 3 insertions(+)
man2/ptrace.2 +3 -0
index c45e569..d051358 100644
@@ -1660,6 +1660,9 @@ In Linux kernels before 2.6.26,
 .BR init (8),
 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,
Signature · 7 lines
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html