Debian Codegraph @

man/error::pass1.7stap

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