From 79dc1deec0e0691a44076d38a3784df11d58a3a8 Mon Sep 17 00:00:00 2001 From: "Frank Ch. Eigler" Date: Wed, 17 Oct 2012 17:46:33 -0400 Subject: [PATCH] documentation: elaborate slightly on .plt probes --- stapprobes.3stap | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/stapprobes.3stap b/stapprobes.3stap index c0f242be0..4e932d916 100644 --- a/stapprobes.3stap +++ b/stapprobes.3stap @@ -134,7 +134,7 @@ l l l. \fBDWARF NON-DWARF\fP kernel.function, .statement kernel.mark -module.function, .statement process.mark +module.function, .statement process.mark, process.plt process.function, .statement begin, end, error, never process.mark \fI(backup)\fP timer perf @@ -767,9 +767,16 @@ If PATH is a process component parameter referring to shared libraries then all processes that map it at runtime would be selected for probing. If PATH is a library component parameter referring to shared libraries then the process specified by the process component would be -selected. A .plt probe will probe functions in the program linkage table +selected. + +.PP +A .plt probe will probe functions in the program linkage table corresponding to the rest of the probe point. .plt can be specified -as a shorthand for .plt("*"). +as a shorthand for .plt("*"). The symbol name is available as a +$$name context variable; function arguments are not available, since +PLTs are processed without debuginfo. + +.PP If the PATH string contains wildcards as in the MPATTERN case, then standard globbing is performed to find all matching paths. In this case, the -- 2.43.5