systemtap точки зондирования (systemtap probe points)
DWARF DEBUGINFO
Resolving some probe points requires DWARF debuginfo or "debug
symbols" for the specific program 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 requirements has to be met on the
computer where script compilation occurs. (See the --use-server
option and the stap-server(8) man page for information about the
remote compilation facility, which allows these requirements to
be met on a different machine.)
The following point lists many of the available probe point
families, to classify them with respect to their need for DWARF
debuginfo for the specific program for that probe point.
DWARF NON-DWARF SYMBOL-TABLE
kernel.function, .statement kernel.mark kernel.function*
module.function, .statement process.mark, process.plt module.function*
process.function, .statement begin, end, error, never process.function*
process.mark* timer
.function.callee perf
python2, python3 procfs
kernel.statement.absolute
AUTO-GENERATED-DWARF kernel.data
kprobe.function
kernel.trace process.statement.absolute
process.begin, .end
netfilter
java
The probe types marked with * asterisks mark fallbacks, where
systemtap can sometimes infer subset or substitute information.
In general, the more symbolic / debugging information available,
the higher quality probing will be available.
