ptrace.2: Clarify that some operations are not present on all architectures

PTRACE_GETREGS, PTRACE_SETGREFS, PTRACE_GETFPREGS,
and PTRACE_GETSPREGS are not present on all architectures.
PTRACE_SYSEMU and PTRACE_SYSEMU_SINGLESTEP are present only
on x86.

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=122383

Simon Paillard <spaillard@debian.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2012-10-25 14:02:19 +02:00
parent 86be5cf6f9
commit 34709982a5
1 changed files with 15 additions and 4 deletions

View File

@ -46,7 +46,7 @@
.\" FIXME Linux 3.1 adds PTRACE_SEIZE, PTRACE_INTERRUPT,
.\" and PTRACE_LISTEN.
.\"
.TH PTRACE 2 2012-08-03 "Linux" "Linux Programmer's Manual"
.TH PTRACE 2 2012-10-25 "Linux" "Linux Programmer's Manual"
.SH NAME
ptrace \- process trace
.SH SYNOPSIS
@ -230,6 +230,10 @@ reversed; that is,
.I data
is ignored and the registers are copied to the address
.IR addr .
.B PTRACE_GETREGS
and
.B PTRACE_GETFPREGS
are not present on all architectures.
.TP
.BR PTRACE_GETSIGINFO " (since Linux 2.3.99-pre6)"
Retrieve information about the signal that caused the stop.
@ -263,6 +267,10 @@ reversed; that is,
.I data
is ignored and the registers are copied from the address
.IR addr .
.B PTRACE_SETREGS
and
.B PTRACE_SETFPREGS
are not present on all architectures.
.TP
.BR PTRACE_SETSIGINFO " (since Linux 2.3.99-pre6)"
Set signal information:
@ -505,9 +513,12 @@ The
.I data
argument is treated as for
.BR PTRACE_CONT .
.RI ( addr
is ignored;
not supported on all architectures.)
The
.I addr
argument is ignored.
These requests are currently
.\" As at 3.7
supported only on x89.
.TP
.B PTRACE_KILL
Send the tracee a