diff options
| author | Szabolcs Nagy <nsz@port70.net> | 2018-07-08 15:16:54 +0200 |
|---|---|---|
| committer | Rich Felker <dalias@aerifal.cx> | 2018-07-17 22:25:08 -0400 |
| commit | df6d9450ea19fd71e52cf5cdb4c85beb73066394 (patch) | |
| tree | 34c80d0c750ec97ce092b1fb0cdf7251f133d16e /arch/m68k/syscall_arch.h | |
| parent | 7ea32a8282b743bb1637b9e1da5f76dcd472a704 (diff) | |
| download | musl-df6d9450ea19fd71e52cf5cdb4c85beb73066394.tar.gz musl-df6d9450ea19fd71e52cf5cdb4c85beb73066394.tar.bz2 musl-df6d9450ea19fd71e52cf5cdb4c85beb73066394.tar.xz musl-df6d9450ea19fd71e52cf5cdb4c85beb73066394.zip | |
add support for arch-specific ptrace command macros
sys/ptrace.h is target specific, use bits/ptrace.h to add target
specific macro definitions.
these macros are kept in the generic sys/ptrace.h even though some
targets don't support them:
PTRACE_GETREGS
PTRACE_SETREGS
PTRACE_GETFPREGS
PTRACE_SETFPREGS
PTRACE_GETFPXREGS
PTRACE_SETFPXREGS
so no macro definition got removed in this patch on any target. only
s390x has a numerically conflicting macro definition (PTRACE_SINGLEBLOCK).
the PT_ aliases follow glibc headers, otherwise the definitions come
from linux uapi headers except ones that are skipped in glibc and
there is no real kernel support (s390x PTRACE_*_AREA) or need special
type definitions (mips PTRACE_*_WATCH_*) or only relevant for linux
2.4 compatibility (PTRACE_OLDSETOPTIONS).
Diffstat (limited to 'arch/m68k/syscall_arch.h')
0 files changed, 0 insertions, 0 deletions