From f2527079ea5622f741cca731194a34a4842f4708 Mon Sep 17 00:00:00 2001 From: "Frank Ch. Eigler" Date: Mon, 10 Sep 2012 13:01:50 -0400 Subject: [PATCH] doc: mention 'context variables' as an alias for 'target variables' --- doc/langref.tex | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/doc/langref.tex b/doc/langref.tex index 7f0962dc9..542b2d2fa 100644 --- a/doc/langref.tex +++ b/doc/langref.tex @@ -369,7 +369,7 @@ in the \texttt{stapprobes(3)}, \texttt{tapset::*(3stap)}, and The probe handler is interpreted relative to the context of each event. For events associated with kernel code, this context may include variables defined -in the source code at that location. These \emph{target variables}\index{target variables} +in the source code at that location. These \emph{target variables}\index{target variables} (or ``context variables'') are presented to the script as variables whose names are prefixed with a dollar sign (\$). They may be accessed only if the compiler used to compile the kernel preserved them, despite optimization. This is the same constraint @@ -1106,10 +1106,7 @@ to not register. Also, statement probes are available only in guru mode. \index{userspace probing} \index{process} Support for userspace probing is supported on kernels that are -configured to include the utrace extensions. Red Hat and CentOS -distributions provide kernels with utrace support enabled. For more -information about utrace, see -\url{http://people.redhat.com/roland/utrace/}. +configured to include the utrace or uprobes extensions. \subsubsection{Begin/end variants} \label{sec:beginendvariants} -- 2.43.5