documentation: elaborate slightly on .plt probes

diff --git a/stapprobes.3stap b/stapprobes.3stap
index c0f242be0960b89aa5675a2974f64e476a139b39..4e932d916c0c5032d429458e90cd7de8335c3a98 100644 (file)
--- 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