Debian Codegraph @

man/error::pass4.7stap

raw
1 .\" t
2 .TH ERROR::PASS4 7stap
3 .SH NAME
4 error::pass4 \- systemtap pass-4 errors
5
6 .\" macros
7 .de SAMPLE
8
9 .nr oldin \\n(.i
10 .br
11 .RS
12 .nf
13 .nh
14 ..
15 .de ESAMPLE
16 .hy
17 .fi
18 .RE
19 .in \\n[oldin]u
20
21 ..
22
23 .SH DESCRIPTION
24 Errors that occur during pass 4 (compilation) have generally only a few
25 causes:
26
27 .TP
28 kernel or OS version changes
29 The systemtap runtime and embedded-C fragments in the tapset library
30 are designed to be portable across a wide range of OS versions. However,
31 incompatibilities can occur when some OS changes occur, such as kernel
32 modifications that change functions, types, or macros referenced
33 by systemtap. Upstream (git://sourceware.org/git/systemtap.git) builds
34 of systemtap are often quickly updated to include relevant fixes, so try
35 getting or making an updated build. Reworded: \fBbuild systemtap from git
36 for use with very young kernels\fP.
37 If the issue persists, report the problem to the systemtap developers.
38
39 .TP
40 buggy embedded-C code
41 Embedded-C code in your own guru-mode script cannot be checked by systemtap,
42 and is passed through verbatim to the compiler. Errors in such snippets of
43 code may be found during the pass-4 compiler invocation, though may be hard
44 to identify by the compiler errors.
45
46 .TP
47 incompatible embedded-C code
48 The interface standards between systemtap-generated code and embedded-C code
49 occasionally change. For example, before version 1.8, arguments were passed
50 using macros
51 .IR THIS->foo " and " THIS->__retvalue
52 but from version 1.8 onward, using
53 .IR STAP_ARG_foo " and " STAP_RETVALUE "."
54 Adjust your embedded-C code to current standards, or use the
55 .IR "stap --compatible=VERSION"
56 option to make systemtap use a different one.
57
58 .TP
59 compiler bugs and mysteries
60 Messages such as "internal compiler error" suggest compiler problems. These
61 should be reported to the compiler developers in the form of a preprocessed
62 .IR ".i"
63 file, plus the compiler command line. To gather relevant information, run
64 .SAMPLE
65 stap -k --vp 0003 -p4 ....
66 .ESAMPLE
67 Systemtap will report the saved temporary directory, and the compiler
68 command line it attempted. Go to the directory to find he main generated
69 file
70 .IR stap_NNNNN_src.c .
71 Force the compiler to produce a preprocessed file with:
72 .SAMPLE
73 make -C /lib/modules/`uname -r`/build M=`pwd` stap_NNNNN_src.i
74 .ESAMPLE
75 (note the
76 .IR .i
77 suffix), and the compiler command line should be in the file
78 .IR ".stap_NNNNN_src.i.cmd" .
79
80 .SH SEE ALSO
81 .nh
82 .nf
83 .IR stap (1),
84 .IR error::reporting (7stap)