1ERROR::PASS5(7stap) ERROR::PASS5(7stap)
2
6 error::pass5 - systemtap pass-5 errors
7
10 Errors that occur during pass 5 (execution) can have a variety of
11 causes.
12 exceptional events during script execution
15 The systemtap translator and runtime include numerous error
16 checks that aim to protect the systems and the users from mis‐
17 takes or transient conditions. The script may deliberately call
18 the error() tapset function to signal a problem. Some memory
19 needed for accessing $context variables may be temporarily
20 unavailable. Consider using the try/catch construct to wrap
21 script fragments in exception-handling code. Consider using the
22 stap --suppress-handler-errors or stap --skip-badvars option.
23 resource exhaustion
26 One of several types of space or time resource limits may be
27 exceeded by the script, including system overload, too many
28 tuples to be stored in an array, etc. Some of the error mes‐
29 sages identify the constraint by macro name, which may be indi‐
30 vidually raised. Consider using the stap --suppress-handler-
31 errors and/or stap -g --suppress-time-limits options. Extend or
32 disable individual resource limits using the stap
33 -DSOME_LIMIT=NNNN option. The stap -t option may identify those
34 probes that are taking too long.
35 remote execution server problems
38 If you use the stap --remote option to direct a systemtap script
39 to be executed somewhere else, ensure that an SSH connection may
40 be made to the remote host, and that it has the current system‐
41 tap runtime installed & available.
42 installation/permission problems
45 It is possible that your installation of systemtap was not cor‐
46 rectly installed. For example, the /usr/bin/staprun program may
47 lack the necessary setuid permissions, or your invoking userid
48 might not have sufficient privileges (root, or stapusr and
49 related group memberships). Environment variables may interfere
50 with locating /usr/libexec/.../stapio.
51 errors from target program
54 The program invoked by the stap -c CMD option may exit with a
55 non-zero code.
56 uncaught exceptions in the target program
59 When using --runtime=dyninst you may encounter an issue where
60 the target program aborts with a message like "terminate called
61 after throwing an instance of 'foo_exception'". This is unfor‐
62 tunately a limitation of Dyninst, which sometimes prevents
63 exceptions from properly unwinding through instrumented code.
64
68 Increasing the verbosity of pass-5 with an option such as --vp 00001
69 can help pinpoint the problem.
70
73 stap(1),
74 http://sourceware.org/systemtap/wiki/TipExhaustedResourceErrors,
75 error::fault(7stap),
76 error::reporting(7stap)
77 ERROR::PASS5(7stap)