System call: <a href="https://en.wikipedia.org/wiki/System_call" rel="nofollow">https://en.wikipedia.org/wiki/System_call</a><p>Strace and similar tools can trace syscalls to see what kernel system calls are made by a process: <a href="https://en.wikipedia.org/wiki/Strace#Similar_tools" rel="nofollow">https://en.wikipedia.org/wiki/Strace#Similar_tools</a><p>Google/syzkaller <a href="https://github.com/google/syzkaller" rel="nofollow">https://github.com/google/syzkaller</a> :<p>> <i>syzkaller ([siːzˈkɔːlə]) is an unsupervised coverage-guided kernel fuzzer. Supported OSes: Akaros, FreeBSD, Fuchsia, gVisor, Linux, NetBSD, OpenBSD, Windows</i><p>Fuschia / Zircon syscalls: <a href="https://fuchsia.dev/fuchsia-src/reference/syscalls" rel="nofollow">https://fuchsia.dev/fuchsia-src/reference/syscalls</a><p>"How does Go make system calls?"
<a href="https://stackoverflow.com/questions/55735864/how-does-go-make-system-calls/55736863#55736863" rel="nofollow">https://stackoverflow.com/questions/55735864/how-does-go-mak...</a>
As an old MS-DOS programmer, I find it very strange that there wasn't a standard call list set down in the days of Unix. IIn MS-DOS, you always knew that function 09h was print $ delimited string at [dx], for example. That's what made it easy to write programs using debug.