LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

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>
This commit is contained in:
Denys Vlasenko 2020-01-21 19:20:45 +01:00 committed by Michael Kerrisk
parent 2b6923ba65
commit 302c512cef
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
man2/ptrace.2
View File

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