1
2ERROR::PASS5(7stap) ERROR::PASS5(7stap)
3
4
5
7 warning::pass5 - systemtap pass-5 warnings
8
9
10
12 Warnings that occur during pass 5 (execution) can have a variety of
13 causes.
14
15
16
17 probe insertion errors
18 With any of the systemtap runtimes, it may be possible that the
19 backends are unable to insert probe points requested by the sys‐
20 temtap script. For example, you may see errors such as
21
22 WARNING: probe [...] registration error (rc -524)
23
24 (524 is a kernel error code for ENOTSUPP). These situations are
25 out of systemtap's control, and result in some probes not re‐
26 ceiving any hits. This may be caused by temporary resource con‐
27 straints or permanent problems. One common permanent problem is
28 such a probe point being placed at instructions that the runtime
29 (kernel kprobes, uprobes or dyninst) cannot decode or intercept.
30 A possible workaround is to move the probe points slightly in
31 the script, so as to target a nearby statement, or a caller, or
32 a callee. See also error::dwarf(7stap).
33
34
36 Increasing the verbosity of pass-5 with an option such as --vp 00001
37 can help pinpoint the problem.
38
39
41 stap(1),
42 http://sourceware.org/systemtap/wiki/TipExhaustedResourceErrors,
43 error::pass5(7stap),
44 error::reporting(7stap)
45 error::dwarf(7stap)
46
47
48
49 ERROR::PASS5(7stap)