From 302c512cef4a5ecb40f748758dd611b053a3654a Mon Sep 17 00:00:00 2001
From: Denys Vlasenko <dvlasenk@redhat.com>
Date: Tue, 21 Jan 2020 19:20:45 +0100
Subject: [PATCH] ptrace.2: PTRACE_EVENT_STOP does not always report SIGTRAP

PTRACE_EVENT_STOP does not always report SIGTRAP, can be the
signal which stopped us

While at it, fix an obvious copy/paste error in
PTRACE_GET_SYSCALL_INFO description.

Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
---
 man2/ptrace.2 | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/man2/ptrace.2 b/man2/ptrace.2
index 0ea9ad7f2..a50b11b98 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -1096,7 +1096,7 @@ system call exit stop.
 .TP
 .BR PTRACE_SYSCALL_INFO_SECCOMP
 The
-.I exit
+.I seccomp
 component of the union contains information relating to a
 .B PTRACE_EVENT_SECCOMP
 stop.
@@ -1566,13 +1566,16 @@ returning with
 and
 .I WSTOPSIG(status)
 returns
-.BR SIGTRAP .
+.BR SIGTRAP
+(or for
+.BR PTRACE_EVENT_STOP ,
+returns the stopping signal if tracee is in a group-stop).
 An additional bit is set in the higher byte of the status word:
 the value
 .I status>>8
 will be
 .PP
-    (SIGTRAP | PTRACE_EVENT_foo << 8).
+    ((PTRACE_EVENT_foo<<8) | SIGTRAP).
 .PP
 The following events exist:
 .TP