| 1 |
.\" t |
| 2 |
.TH ERROR::PASS2 7stap |
| 3 |
.SH NAME |
| 4 |
error::pass2 \- systemtap pass-2 errors |
| 5 |
|
| 6 |
.SH DESCRIPTION |
| 7 |
Errors that occur during pass 2 (elaboration) can have a variety of causes. |
| 8 |
Common types include: |
| 9 |
|
| 10 |
.TP |
| 11 |
missing debuginfo |
| 12 |
The script requires debuginfo to resolve a probe point, but could not |
| 13 |
find any. See |
| 14 |
.IR error::dwarf (7stap) |
| 15 |
and |
| 16 |
.IR warning::debuginfo (7stap) |
| 17 |
for more details. |
| 18 |
|
| 19 |
.TP |
| 20 |
unavailable probe point classes |
| 21 |
Some types of probe points are only available on certain system versions, |
| 22 |
architectures, and configurations. For example, user-space |
| 23 |
.IR process.* |
| 24 |
probes may require utrace or uprobes capability in the kernel for this |
| 25 |
architecture. |
| 26 |
|
| 27 |
.TP |
| 28 |
unavailable probe points |
| 29 |
Some probe points may be individually unavailable even when their class is |
| 30 |
fine. For example, |
| 31 |
.IR kprobe.function("foobar") |
| 32 |
may fail if function |
| 33 |
.IR foobar |
| 34 |
does not exist in the kernel any more. Debugging or symbol data may be absent for |
| 35 |
some types of |
| 36 |
.IR .function " or " .statement |
| 37 |
probes; check for availability of debuginfo. Try the |
| 38 |
.IR stap\-prep |
| 39 |
program to download possibly-required debuginfo. |
| 40 |
Use a wildcard parameter such as |
| 41 |
.I stap \-l 'kprobe.function("*foo*")' |
| 42 |
to locate still-existing variants. Use |
| 43 |
.IR ! " or " ? |
| 44 |
probe point suffixes to denote optional / preferred-alternatives, to let |
| 45 |
the working parts of a script continue. |
| 46 |
|
| 47 |
.TP |
| 48 |
typos |
| 49 |
There might be a spelling error in the probe point name ("sycsall" vs. |
| 50 |
"syscall"). Wildcard probes may not find a match at all in the |
| 51 |
tapsets. Recheck the names using |
| 52 |
.IR "stap \-l PROBEPOINT" . |
| 53 |
Another common mistake is to use the |
| 54 |
.IR . |
| 55 |
operator instead of the correct |
| 56 |
.IR \-> |
| 57 |
when dereferencing context variable subfields or pointers: |
| 58 |
.IR $foo\->bar\->baz |
| 59 |
even if in C one would say |
| 60 |
.IR foo\->bar.baz . |
| 61 |
|
| 62 |
.TP |
| 63 |
unavailable context variables |
| 64 |
Systemtap scripts often wish to refer to variables from the context of the |
| 65 |
probed programs using |
| 66 |
.IR $variable |
| 67 |
notation. These variables may not always be available, depending on versions |
| 68 |
of the compiler, debugging/optimization flags used, architecture, etc. Use |
| 69 |
.IR "stap \-L PROBEPOINT" |
| 70 |
to list available context variables for given probes. Use the |
| 71 |
.IR @defined() |
| 72 |
expression to test for the resolvability of a context variable expression. |
| 73 |
Consider using the |
| 74 |
.IR "stap \-\-skip\-badvars" |
| 75 |
option to silently replace misbehaving context variable expressions with zero. |
| 76 |
Experiment with the |
| 77 |
.IR "stap \-\-prologue\-searching" |
| 78 |
option. |
| 79 |
|
| 80 |
.TP |
| 81 |
module cache inconsistencies |
| 82 |
Occasionally, the systemtap module cache ($HOME/.systemtap/cache) might |
| 83 |
contain obsolete information from a prior system configuration/version, |
| 84 |
and produce false results as systemtap attempts to reuse it. Retrying |
| 85 |
with |
| 86 |
.IR "stap \-\-poison\-cache ..." |
| 87 |
forces new information to be generated. |
| 88 |
.BR Note: |
| 89 |
this should not happen and likely represents a systemtap bug. Please |
| 90 |
report it. |
| 91 |
|
| 92 |
.SH GATHERING MORE INFORMATION |
| 93 |
Increasing the verbosity of pass-2 with an option such as |
| 94 |
.IR "--vp 02" |
| 95 |
can help pinpoint the problem. |
| 96 |
|
| 97 |
.SH SEE ALSO |
| 98 |
.nh |
| 99 |
.nf |
| 100 |
.IR stap (1), |
| 101 |
.IR stap-prep (1), |
| 102 |
.IR stapprobes (3stap), |
| 103 |
.IR probe::* (3stap), |
| 104 |
.IR error::dwarf (7stap), |
| 105 |
.IR error::inode-uprobes (7stap), |
| 106 |
.IR warning::debuginfo (7stap), |
| 107 |
.IR error::reporting (7stap) |