A stress test of 50 million syscalls revealed that a C++ implementation silently accumulated over 4 GB of memory and crashed without any alerts, while an equivalent Rust version remained stable, highlighting how gradual memory bloat can evade monitoring and cause hidden failures in high‑concurrency services.
This article explains how system calls differ from regular function calls, demonstrates a simple x86_64 hello‑world program that uses the syscall instruction, and details how Linux maps syscall numbers to kernel functions via the MSR LSTAR register.
This article explains the major differences in Go's syscall library on Linux and Windows, covering system‑call interfaces, library structure, error handling, portability, example code, and recommended higher‑level alternatives for cross‑platform development.
This article walks through a Go example that uses the os, os/exec, and syscall packages to locate the ls binary, set arguments and environment, and then replace the current process with ls via syscall.Exec, explaining each step and its practical implications.
This article explains how to obtain a file's owner information in Go by using the os package together with system calls, detailing the required steps, providing a complete code example, and highlighting platform considerations and typical use cases.
Go versions 1.19.3 and 1.18.8 were released, each containing a security fix that addresses unsanitized NUL handling in the os/exec and syscall packages, particularly on Windows, and includes runtime error corrections.
This article explains why Go programs that spawn child processes can leave orphaned processes after a kill, and demonstrates two robust solutions: creating a new process group with syscall.Kill and using Linux prctl (via CGO or RawSyscall) to ensure child processes terminate when the parent exits.
This article explains how Linux system calls work, compares their overhead to regular function calls, and details the three implementation methods—software interrupts, fast syscall instructions, and the virtual dynamic shared object (vDSO)—including their performance trade‑offs and practical usage.
This article explains how Linux implements system calls via software interrupts, fast syscall/sysenter instructions, and the virtual dynamic shared object (vDSO), comparing their performance to regular function calls and showing concrete code examples and step‑by‑step execution details.
Go’s syscall mechanism uses assembly‑implemented entry functions like Syscall and Syscall6 to invoke the kernel, while the runtime’s entersyscall and exitsyscall hooks notify the scheduler, allowing P resources to be released during blocking calls and handling privileged low‑level syscalls separately.
This article explains three ways to perform Linux system calls—using glibc wrapper functions, the low‑level syscall interface, and inline assembly with the int 0x80 instruction—illustrating each method with a chmod example, error handling, and code snippets.
