1ERROR::PASS4(7stap)                                        ERROR::PASS4(7stap)
2
3
4

NAME

6       error::pass4 - systemtap pass-4 errors
7
8
9

DESCRIPTION

11       Errors that occur during pass 4 (compilation) have generally only a few
12       causes:
13
14
15       kernel or OS version changes
16              The systemtap runtime and embedded-C  fragments  in  the  tapset
17              library  are  designed  to be portable across a wide range of OS
18              versions.  However, incompatibilities can  occur  when  some  OS
19              changes  occur,  such  as kernel modifications that change func‐
20              tions, types,  or  macros  referenced  by  systemtap.   Upstream
21              (git://sourceware.org/git/systemtap.git) builds of systemtap are
22              often quickly updated to include relevant fixes, so try  getting
23              or  making  an updated build.  If the issue persists, report the
24              problem to the systemtap developers.
25
26
27       buggy embedded-C code
28              Embedded-C code in your own guru-mode script cannot  be  checked
29              by  systemtap,  and  is passed through verbatim to the compiler.
30              Errors in such snippets of code may be found during  the  pass-4
31              compiler  invocation, though may be hard to identify by the com‐
32              piler errors.
33
34
35       incompatible embedded-C code
36              The interface standards  between  systemtap-generated  code  and
37              embedded-C  code  occasionally change.  For example, before ver‐
38              sion 1.8, arguments  were  passed  using  macros  THIS->foo  and
39              THIS->__retvalue but from version 1.8 onward, using STAP_ARG_foo
40              and STAP_RETVALUE.  Adjust your embedded-C code to current stan‐
41              dards,  or use the stap --compatible=VERSION option to make sys‐
42              temtap use a different one.
43
44
45       compiler bugs and mysteries
46              Messages such as  "internal  compiler  error"  suggest  compiler
47              problems.   These  should be reported to the compiler developers
48              in the form of a preprocessed .i file, plus the compiler command
49              line.  To gather relevant information, run
50
51              stap -k --vp 0003 -p4 ....
52
53              Systemtap  will  report  the  saved temporary directory, and the
54              compiler command line it attempted.  Go to the directory to find
55              he  main generated file stap_NNNNN_src.c.  Force the compiler to
56              produce a preprocessed file with:
57
58              make -C /lib/modules/`uname -r`/build M=`pwd` stap_NNNNN_src.i
59
60              (note the .i suffix), and the compiler command line should be in
61              the file .stap_NNNNN_src.i.cmd.
62
63

SEE ALSO

65       stap(1),
66       error::reporting(7stap)
67
68
69
70                                                           ERROR::PASS4(7stap)
Impressum