1ERROR::PASS1(7stap) ERROR::PASS1(7stap)
2
6 error::pass1 - systemtap pass-1 errors
7
10 Errors that occur during pass 1 (parsing) usually mean a basic syntax
11 error of some sort occurred in the systemtap script. There are several
12 classes of problems possible:
13 plain syntax error
16 The systemtap script parser detects a large variety of errors,
17 such as missing operands, bad punctuation. It tries to list
18 what kinds of tokens it was expecting to see, and will show the
19 region of the source code with the problem. Please review the
20 stap(1) man page and/or the tutorial, to correct the script's
21 syntax.
22 grammar ambiguities
25 There is at least one known ambiguity in the systemtap grammar.
26 It relates to the optionality of ; (semicolon) separators
27 between statements, and the ++ and -- increment/decrement opera‐
28 tors. If the parser indicates an error, consider adding some
29 explicit ; separators between nearby statements and try again.
30 missing command line arguments
33 A systemtap script that uses the $N and @N constructs for sub‐
34 stituting in command-line options may fail if not enough options
35 were given on the stap command line.
36 compatibility changes
39 Some versions of systemtap have changed the language incompati‐
40 bly, for example by adding the try/catch keywords for exception
41 handling. In such cases, rerun systemtap with the --compatibil‐
42 ity=VERSION option, substituting the last systemtap version
43 where your script was known to work. You may also check the
44 release-history NEWS file for compatibility changes.
45
48 Increasing the verbosity of pass-1 with an option such as --vp 1 can
49 help pinpoint the problem.
50
53 stap(1),
54 error::reporting(7stap)
55 ERROR::PASS1(7stap)