From 2019744dac517865844fbe6cfd912616b4f8bbdb Mon Sep 17 00:00:00 2001 From: Stan Cox Date: Thu, 25 Feb 2021 16:56:07 -0500 Subject: [PATCH] Fix misspellings in stap manpage. --- man/stap.1.in | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/man/stap.1.in b/man/stap.1.in index 0ae859c64..d410e9c60 100644 --- a/man/stap.1.in +++ b/man/stap.1.in @@ -96,7 +96,7 @@ The program is the front-end to the Systemtap tool. It accepts probing instructions written in a simple domain-specific language, translates those instructions into C code, compiles this C code, and loads the -resulting module into a running Linux kernel or a DynInst user-space +resulting module into a running Linux kernel or a Dyninst user-space mutator, to perform the requested system trace/probe functions. You can supply the script in a named file (FILENAME), from standard input (use \- instead of FILENAME), or from the command line (using \-e @@ -2083,7 +2083,7 @@ is used for user space addresses. @kderef(SIZE, addr) @uderef(SIZE, addr) .ESAMPLE -This will interpert +This will interpret .I addr as a kernel/user address and read .I SIZE @@ -2653,7 +2653,7 @@ now includes two new prototype backends: \fI\-\-runtime=dyninst\fR and at runtime. This backend does not use kernel modules, and does not require root privileges, but is restricted with respect to the kinds of probes and other constructs that a script may use. \fIdyninst\fR runtime operates in -target-attach mode, so it does requirea \fI\-c COMMAND\fR or \fI\-x PID\fR +target-attach mode, so it does require a \fI\-c COMMAND\fR or \fI\-x PID\fR process. For example: .SAMPLE stap \-\-runtime=dyninst \-c 'stap \-V' \\ -- 2.43.5