Skip to contentSkip to conversation

ptrace.2: pfix

PATCH Applied David Prévot 2 participants 4 messages Sep 4, 2013 2 messages not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ptrace.2: pfix

---
 man2/ptrace.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
man2/ptrace.2 +1 -1
index 60d5345..7ad5ce8 100644
@@ -1231,7 +1231,7 @@ Stop induced by
 .B PTRACE_INTERRUPT
 command, or group-stop, or initial ptrace-stop when a new child is attached
 (only if attached using
-.BR PTRACE_SEIZE ).
+.BR PTRACE_SEIZE ),
 or
 .B PTRACE_EVENT_STOP
 if
Signature · 6 lines
1.8.4.rc3

--
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

A message that is not in the archive (sent off-list or not yet received): 1378259828-12785-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org

#2 lore raw

PATCH 1/1 ptrace.2: ffix

---
 man2/ptrace.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
man2/ptrace.2 +1 -1
index 7ad5ce8..f9118bf 100644
@@ -1095,7 +1095,7 @@ then it is definitely a group-stop.
 killed the tracee.)
 .LP
 If tracee was attached using
-.IR PTRACE_SEIZE ,
+.BR PTRACE_SEIZE ,
 group-stop is indicated by
 .BR PTRACE_EVENT_STOP :
 .IR "status>>16 == PTRACE_EVENT_STOP" .
Signature · 6 lines
1.8.4.rc3

--
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

A message that is not in the archive (sent off-list or not yet received): 1378261307-19248-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org

#4 lore raw

Re: [PATCH] ptrace.2: ffix

Applied. Thanks, David.

Cheers,

Michael

Quoted 10 lines · David Prévot
---
 man2/ptrace.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
man2/ptrace.2 +0 -0
index 7ad5ce8..f9118bf 100644

man2/ptrace.2 then it is definitely a group-stop. · line 1101

Quoted 8 lines
man2/ptrace.2 +1 -1
@@ -1095,7 +1095,7 @@ then it is definitely a group-stop.
 killed the tracee.)
 .LP
 If tracee was attached using
-.IR PTRACE_SEIZE ,
+.BR PTRACE_SEIZE ,
 group-stop is indicated by
 .BR PTRACE_EVENT_STOP :
 .IR "status>>16 == PTRACE_EVENT_STOP" .

--
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

#5 lore raw
In reply to a message not in the archive

Applied. Thanks, David.

Cheers,

Michael

Quoted 10 lines · David Prévot
---
 man2/ptrace.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
man2/ptrace.2 +0 -0
index 60d5345..7ad5ce8 100644

man2/ptrace.2 Stop induced by · line 1237

Quoted 8 lines
man2/ptrace.2 +1 -1
@@ -1231,7 +1231,7 @@ Stop induced by
 .B PTRACE_INTERRUPT
 command, or group-stop, or initial ptrace-stop when a new child is attached
 (only if attached using
-.BR PTRACE_SEIZE ).
+.BR PTRACE_SEIZE ),
 or
 .B PTRACE_EVENT_STOP
 if

--
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