From 61770a9e38780d313a5323797ca6e92a1c151dd9 Mon Sep 17 00:00:00 2001 From: Weber Zhang Date: Wed, 7 Nov 2018 16:59:48 +0800 Subject: [PATCH] Fix up one mistake `/proc/pid/systemcall` -> `/proc/${pid}/syscall` --- SysCall/linux-syscall-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SysCall/linux-syscall-1.md b/SysCall/linux-syscall-1.md index cb67a18..ae1b6ba 100644 --- a/SysCall/linux-syscall-1.md +++ b/SysCall/linux-syscall-1.md @@ -182,7 +182,7 @@ The `ltrace` util displays a set of userspace calls of a program. The `fopen` fu write@SYS(1, "Hello World!\n\n", 14) = 14 ``` -Yes, system calls are ubiquitous. Each program needs to open/write/read files and network connections, allocate memory, and many other things that can be provided only by the kernel. The [proc](https://en.wikipedia.org/wiki/Procfs) file system contains special files in a format: `/proc/pid/systemcall` that exposes the system call number and argument registers for the system call currently being executed by the process. For example, pid 1 is [systemd](https://en.wikipedia.org/wiki/Systemd) for me: +Yes, system calls are ubiquitous. Each program needs to open/write/read files and network connections, allocate memory, and many other things that can be provided only by the kernel. The [proc](https://en.wikipedia.org/wiki/Procfs) file system contains special files in a format: `/proc/${pid}/syscall` that exposes the system call number and argument registers for the system call currently being executed by the process. For example, pid 1 is [systemd](https://en.wikipedia.org/wiki/Systemd) for me: ``` $ sudo cat /proc/1/comm