From c5ae4566967932aa36f97a620d1571a251ff093f Mon Sep 17 00:00:00 2001 From: "Frank Ch. Eigler" Date: Mon, 13 Apr 2015 21:04:40 -0400 Subject: [PATCH] man stapprobes: emphasize that dwarf debuginfo is probe-point-specific (This is to further disabuse folks of the notion that kernel-debuginfo is always needed.) --- man/stapprobes.3stap | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/man/stapprobes.3stap b/man/stapprobes.3stap index 73456dcbb..300c6b6e0 100644 --- a/man/stapprobes.3stap +++ b/man/stapprobes.3stap @@ -121,7 +121,7 @@ all of which are probed. .SH DWARF DEBUGINFO Resolving some probe points requires DWARF debuginfo or "debug -symbols" for the specific part being instrumented. For some others, +symbols" for the \fIspecific program\fR being instrumented. For some others, DWARF is automatically synthesized on the fly from source code header files. For others, it is not needed at all. Since a systemtap script may use any mixture of probe points together, the union of their DWARF @@ -131,7 +131,8 @@ occurs. (See the \fI\-\-use\-server\fR option and the \fBstap-server\ which allows these requirements to be met on a different machine.) .PP The following point lists many of the available probe point families, -to classify them with respect to their need for DWARF debuginfo. +to classify them with respect to their need for DWARF debuginfo for +the specific program for that probe point. .TS l l l. -- 2.43.5