http://sources.redhat.com/systemtap/tutorial/node27.html
- semantic error: probe point mismatch at position N,
while resolving probe point foo
A probe point was named that
neither directly understood by systemtap, nor defined as an alias by a
tapset script. The divergence from the ``tree'' of probe point
namespace is at position N (starting with zero at left).
- semantic error: no match for probe point, while resolving
probe point foo
A probe point cannot be resolved for any of
a variety of reasons. It may be a debuginfo-based probe point such as
kernel.function("foobar") where no foobar
function was
found. This can occur if the script specifies a wildcard on function
names, or an invalid file name or source line number.
- semantic error: unresolved target-symbol _expression_
A
target variable was referred to in a probe handler that was not
resolvable. Or, a target variable is not valid at all in a context
such as a script function. This variable may have been elided by an
optimizing compiler, or may not have a suitable type, or there might
just be an annoying bug somewhere. Try again with a slightly
different probe point (use statement() instead of
function()) to search for a more cooperative neighbour
in the
same area.
- semantic error: libdwfl failure
There was a
problem processing the debugging information. It may simply be
missing, or may have some consistency / correctness problems. Later
compilers tend to produce better debugging information, so if you can
upgrade and recompile your kernel/application, it may help.
- semantic error: cannot find foo debuginfo
Similarly,
suitable debugging information was not found. Check that your kernel
build/installation includes a matching version of debugging data.
|
