2 .TH WARNING::DEBUGINFO 7stap
4 warning::debuginfo \- systemtap missing-debuginfo warnings
24 For many symbolic probing operations, systemtap needs DWARF debuginfo for
25 the relevant binaries. This often includes resolving function/statement
26 probes, or $context variables in related handlers. DWARF debuginfo may
27 be found in the original binaries built during compilation, or may have
28 been split into separate files. The
29 .IR SYSTEMTAP_DEBUGINFO_PATH
30 environment variable affects where systemtap looks for these files.
32 If your operating system came from a distributor, check with them if
33 debuginfo packages or variants are available. If your distributor does
34 not have debuginfo-equipped binaries at all, you may need to rebuild it.
38 library to process ELF/DWARF files. The version of elfutils used by systemtap
39 is the number after the slash in the
44 Systemtap translator/driver (version 2.3/0.156, rpm 2.3-1.fc19)
45 Copyright (C) 2005-2014 Red Hat, Inc. and others
48 This indicates systemtap version 2.3 with elfutils version 0.156.
52 For scripts that target the kernel, systemtap may search for the
54 file created during its original build. This is distinct from the
55 boot-loader's compressed/stripped
57 file, and much larger. If you have a hand-built kernel, make sure
59 .IR CONFIG_DEBUG_INFO=y
64 For scripts that target user-space, systemtap may search for debuginfo.
65 If you have hand-built binaries, use
71 On some systems, binaries may be compiled with a subset of debuginfo
72 useful for function tracing and backtraces. This 'Minidebuginfo' is
73 a xz compressed section labeled .gnu_debugdata. Support for
74 minidebuginfo relies on elfutils version 0.156 or later.
78 On some systems, debuginfo may be available, but compressed into
80 sections. Support for compressed debuginfo relies on elfutils
81 version 0.153 or later.
85 In some cases, a script may be altered to avoid requiring debuginfo.
86 For example, as script that uses
88 probes could try instead
89 .IR "probe nd_syscall.*"
90 (for non-DWARF syscall): these work similarly, and use more intricate
91 (fragile) tapset functions to extract system call arguments. Another
92 option is use of compiled-in instrumentation such as kernel tracepoints
95 markers in libraries or executables, which do not require debuginfo.
96 If debuginfo was required for resolving a complicated
98 expression, it may be possible to use
99 .IR @cast(var,"foo","foo.h")->foo->bar
100 to synthesize debuginfo for that type from a header file.
104 On some platforms, systemtap may advise what commands to run, in order
105 to download needed debuginfo. Another possibility is to invoke systemtap
107 .IR \-\-download\-debuginfo
111 script included with systemtap may be able to download the
112 appropriate kernel debuginfo. Another possibility is to install and
115 remote-compilation instance on a machine on your network, where
116 debuginfo and compilation resources can be centralized. Try the
117 .IR "stap --use-server"
118 option, in case such a server is already running.
128 .IR error::dwarf (7stap),
129 .IR error::reporting (7stap),
130 .IR error::contextvars (7stap),
131 .IR http://fedorahosted.org/elfutils ,
132 .IR http://fedoraproject.org/wiki/Features/MiniDebugInfo