1scmp_sys_resolver(1)       libseccomp Documentation       scmp_sys_resolver(1)
2
3
4

NAME

6       scmp_sys_resolver - Resolve system calls
7

SYNOPSIS

9       scmp_sys_resolver [-h] [-a ARCH ] [-t] SYSCALL_NAME | SYSCALL_NUMBER
10

DESCRIPTION

12       This  command  resolves both system call names and numbers with respect
13       to the given architecture supplied in the optional ARCH  argument.   If
14       the  architecture  is  not supplied on the command line then the native
15       architecture is used.  If the "-t" argument is specified along  with  a
16       system  call name, then the system call will be translated as necessary
17       for the given architecture.  The "-t" argument has no effect if a  sys‐
18       tem call number is specified.
19
20       In some combinations of architecture and system call, a negative system
21       call number will be displayed.  A negative system call number indicates
22       that  the  system call is not defined for the given architecture and is
23       treated in a special manner by libseccomp depending on the operation.
24
25       -a ARCH
26              The architecture to use for resolving the  system  call.   Valid
27              ARCH  values  are  "x86",  "x86_64",  "x32",  "arm",  "aarch64",
28              "mips",    "mipsel",    "mips64",    "mipsel64",    "mips64n32",
29              "mipsel64n32",  "parisc", "parisc64", "ppc", "ppc64", "ppc64le",
30              "s390" and "s390x".
31
32       -t     If necessary, translate the system call name to the proper  sys‐
33              tem call number, even if the system call name is different, e.g.
34              socket(2) on x86.
35
36       -h     A simple one-line usage display.
37

EXIT STATUS

39       Returns zero on success, errno values on failure.
40

NOTES

42       The libseccomp project site, with more information and the source  code
43       repository,  can  be  found  at  https://github.com/seccomp/libseccomp.
44       This tool, as well as the libseccomp library, is currently under devel‐
45       opment,  please  report any bugs at the project site or directly to the
46       author.
47

AUTHOR

49       Paul Moore <paul@paul-moore.com>
50
51
52
53paul@paul-moore.com               23 May 2013             scmp_sys_resolver(1)
Impressum