| 1 | .TH "scmp_sys_resolver" 1 "23 May 2013" "paul@paul-moore.com" "libseccomp Documentation" |
| 2 | .\" ////////////////////////////////////////////////////////////////////////// |
| 3 | .SH NAME |
| 4 | .\" ////////////////////////////////////////////////////////////////////////// |
| 5 | scmp_sys_resolver \- Resolve system calls |
| 6 | .\" ////////////////////////////////////////////////////////////////////////// |
| 7 | .SH SYNOPSIS |
| 8 | .\" ////////////////////////////////////////////////////////////////////////// |
| 9 | .B scmp_sys_resolver |
| 10 | [\-h] [\-a |
| 11 | .I ARCH |
| 12 | ] [\-t] |
| 13 | .I SYSCALL_NAME |
| 14 | | |
| 15 | .I SYSCALL_NUMBER |
| 16 | .\" ////////////////////////////////////////////////////////////////////////// |
| 17 | .SH DESCRIPTION |
| 18 | .\" ////////////////////////////////////////////////////////////////////////// |
| 19 | .P |
| 20 | This command resolves both system call names and numbers with respect to the |
| 21 | given architecture supplied in the optional |
| 22 | .I ARCH |
| 23 | argument. If the architecture is not supplied on the command line then the |
| 24 | native architecture is used. If the "\-t" argument is specified along with a |
| 25 | system call name, then the system call will be translated as necessary for the |
| 26 | given architecture. The "\-t" argument has no effect if a system call number |
| 27 | is specified. |
| 28 | .P |
| 29 | In some combinations of architecture and system call, a negative system call |
| 30 | number will be displayed. A negative system call number indicates that the |
| 31 | system call is not defined for the given architecture and is treated in a |
| 32 | special manner by libseccomp depending on the operation. |
| 33 | .TP |
| 34 | .B \-a \fIARCH |
| 35 | The architecture to use for resolving the system call. Valid |
| 36 | .I ARCH |
| 37 | values are "x86", "x86_64", "x32", and "arm". |
| 38 | .TP |
| 39 | .B \-t |
| 40 | If necessary, translate the system call name to the proper system call number, |
| 41 | even if the system call name is different, e.g. socket(2) on x86. |
| 42 | .TP |
| 43 | .B \-h |
| 44 | A simple one-line usage display. |
| 45 | .\" ////////////////////////////////////////////////////////////////////////// |
| 46 | .SH EXIT STATUS |
| 47 | .\" ////////////////////////////////////////////////////////////////////////// |
| 48 | Returns zero on success, errno values on failure. |
| 49 | .\" ////////////////////////////////////////////////////////////////////////// |
| 50 | .SH NOTES |
| 51 | .\" ////////////////////////////////////////////////////////////////////////// |
| 52 | .P |
| 53 | The libseccomp project site, with more information and the source code |
| 54 | repository, can be found at https://github.com/seccomp/libseccomp. This tool, |
| 55 | as well as the libseccomp library, is currently under development, please |
| 56 | report any bugs at the project site or directly to the author. |
| 57 | .\" ////////////////////////////////////////////////////////////////////////// |
| 58 | .SH AUTHOR |
| 59 | .\" ////////////////////////////////////////////////////////////////////////// |
| 60 | Paul Moore <paul@paul-moore.com> |