mirror of https://github.com/mkerrisk/man-pages
ptrace.2: Note use of 'data' for PTRACE_SYS{CALL,EMU} and PTRCAE_*_SINGLESTEP
These operations use the 'data' argument as a signal number, like PTRACE_CONT. Reported-by: Mike Frysinger <vapier@gentoo.org> Reported-by: Roland McGrath <roland@redhat.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
48e4cfa0de
commit
94cffcd707
|
@ -331,6 +331,10 @@ then do another
|
|||
.B PTRACE_SYSCALL
|
||||
and inspect the return value of
|
||||
the system call at the second stop.
|
||||
The
|
||||
.I data
|
||||
argument is treated as for
|
||||
.BR PTRACE_CONT .
|
||||
(\fIaddr\fP is ignored.)
|
||||
.TP
|
||||
.BR PTRACE_SYSEMU ", " PTRACE_SYSEMU_SINGLESTEP " (since Linux 2.6.14)"
|
||||
|
@ -344,7 +348,11 @@ do the same
|
|||
but also singlestep if not a syscall.
|
||||
This call is used by programs like
|
||||
User Mode Linux that want to emulate all the child's system calls.
|
||||
(\fIaddr\fP and \fIdata\fP are ignored;
|
||||
The
|
||||
.I data
|
||||
argument is treated as for
|
||||
.BR PTRACE_CONT .
|
||||
(\fIaddr\fP is ignored;
|
||||
not supported on all architectures.)
|
||||
.TP
|
||||
.B PTRACE_KILL
|
||||
|
|
Loading…
Reference in New Issue