scmp_sys_resolver(1)

💖 scmp_sys_resolver — the libseccomp girlie's guide 💖

okay so bestie, this is scmp_sys_resolver(1), and yes it's part of the libseccomp documentation. it resolves system calls. that's the whole vibe. let's go 🦋

---

✨ NAME ✨

scmp_sys_resolver — resolve system calls 💅

---

🎀 SYNOPSIS 🎀

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

---

🌸 DESCRIPTION 🌸

so this command resolves both system call names AND numbers with respect to whatever architecture you hand it in the optional ARCH argument. no cap. 💖

if you don't supply an architecture on the command line, it just uses the native architecture. easy. default behavior, we love her.

now — if you pass -t along with a system call name, then the system call gets translated as necessary for the given architecture. that's the whole point of -t. but — and this is important bestie — -t has no effect if you specified a system call number. none. zero. she said "not today." 😭

and here's the spicy part: in some combinations of architecture and system call, you'll get a negative system call number displayed. a negative number means the system call is not defined for that architecture, and libseccomp treats it in a special manner depending on the operation. so if you see a negative, don't panic — that's the signal. 🚨

---

💅 OPTIONS 💅

• -a ARCH — the architecture to use for resolving the system call. the valid ARCH values are "x86", "x86_64", "x32", "arm", "aarch64", "loongarch64", "m68k", "mips", "mipsel", "mips64", "mipsel64", "mips64n32", "mipsel64n32", "parisc", "parisc64", "ppc", "ppc64", "ppc64le", "s390", "s390x", "sheb" and "sh". (yes, all of them. pick your fighter. 👑)
• -t — if necessary, translate the system call name to the proper system call number, even if the system call name is different. like, for example, socket(2) on x86. it's giving "same energy, different number." 🔥
• -h — a simple one-line usage display. short, sweet, iconic. ✨

---

🫶 EXIT STATUS 🫶

returns zero on success, and errno values on failure. that's it, that's the whole story. 💀

---

🧚 NOTES 🧚

the libseccomp project site — with more info and the source code repository — lives at https://github.com/seccomp/libseccomp. go visit her, she's lovely. 🌈

this tool, as well as the libseccomp library, is currently under development, so please report any bugs at the project site or directly to the author. bestie we are actively building, ty for your patience 🙈

---

⭐ AUTHOR ⭐

Paul Moore <paul@paul-moore.com> — the main character who made all this happen 👑

---

ok that's the whole page, you're basically a seccomp expert now, no notes 💖

and a lil sign-off from the original footer: this one's brought to you by paul@paul-moore.com, dated 23 May 2013, and it's scmp_sys_resolver(1) — periodt. 🎀🦋