error::dwarf(7stap) [centos man page]

ERROR::DWARF(7stap)													       ERROR::DWARF(7stap)

NAME

       error::dwarf - dwarf debuginfo quality problems

DESCRIPTION

       Systemtap  sometimes  relies  on  ELF/DWARF  debuginfo  for  programs being instrumented to locate places to probe, or context variables to
       read/write, just like a symbolic debugger does.	Even though examination of the program's source code may show  variables  or  lines  where
       probes  may  be desired, the compiler must preserve information about them for systemtap (or a debugger such as gdb) to get pinpoint access
       to the desired information.  If a script requires such data, but the compiler did not preserve enough of it, pass-2 errors may result.

       Common conditions that trigger these problems include;

       compiler version
	      Prior to GCC version 4.5, debuginfo quality was fairly limited.  Often developers were advised to build their programs with  -O0	-g
	      flags  to disable optimization.  GCC version 4.5 introduced a facility called "variable-tracking assignments" that allows it to gen-
	      erate high-quality debuginfo under full -O2 -g optimization.  It is not perfect, but much better than before.   Note  that,  due	to
	      another gcc bug (PR51358) -O0 -g can actually sometimes make debuginfo quality worse than for -O2 -g.

       function inlining
	      Even  modern gcc sometimes has problems with parameters for inlined functions.  It may be necessary to change the script to probe at
	      a slightly different place (try a .statement() probe, instead of a .function() probe, somewhere a few source lines into the body	of
	      the inlined function.  Or try putting a probe at the call site of the inlined function.  Or use the if @defined($var) { ... } script
	      language construct to test for the resolvability of the context variable before using it.

       instruction reordering
	      Heavily optimized code often smears the instructions from multiple source statements together.  This can	leave  systemtap  with	no
	      place  to choose to place a probe, especially a statement probe specified by line number.  Systemtap may advise to try a nearby line
	      number, but these may not work well either.  Consider placing a probe by a statement wildcard or line number range.

ALTERNATIVES

       In order to reduce reliance on ELF/DWARF debuginfo, consider the use of statically compiled-in instrumentation, such as kernel tracepoints,
       or <sys/sdt.h> userspace markers.  Such instrumentation hook sites are relatively low cost (just one NOP instruction for sdt.h), and nearly
       guarantee the availability of parameter data and a reliable probe site, all without reliance on debuginfo.

SEE ALSO

       stap(1),
       http://dwarfstd.org/,
       http://sourceware.org/systemtap/wiki/TipContextVariables,
       http://gcc.gnu.org/wiki/Var_Tracking_Assignments,
       warning::debuginfo(7stap),
       error::reporting(7stap)

															       ERROR::DWARF(7stap)

ERROR::SDT(7stap)														 ERROR::SDT(7stap)

NAME

       error::sdt - <sys/sdt.h> marker failures

DESCRIPTION

       Systemtap's <sys/sdt.h> probes are modeled after the dtrace USDT API, but are implemented differently.  They leave a only a NOP instruction
       in the userspace program's text segment, and add an ELF note to the binary with metadata.  This metadata describes the  marker's  name  and
       parameters.   This  encoding  is  designed to be parseable by multiple tools (not just systemtap: GDB, the GNU Debugger, also contains sup-
       port).  These allow the tools to find parameters and their types, wherever they happen to reside, even without DWARF debuginfo.

       The reason finding parameters is tricky is because the STAP_PROBE / DTRACE_PROBE markers store an assembly language expression for each op-
       erand,  as  a result of use of gcc inline-assembly directives.  The compiler is given a broad gcc operand constraint string ("nor") for the
       operands, which usually works well.  Usually, it does not force the compiler to load the parameters into or out of registers,  which  would
       slow  down  an instrumented program.  However, some instrumentation sites with some parameters do not work well with the default "nor" con-
       straint.

       unresolveable at run-time
	      GCC may emit strings that an assembler could resolve (from the context of compiling the original program), but a run-time tool  can-
	      not.   For example, the operand string might refer to a label of a local symbol that is not emitted into the ELF object file at all,
	      which leaves no trace for the run-time.  Reference to such parameters from within systemtap can result in "SDT asm  not  understood"
	      errors.

       too complicated expression
	      GCC  might  synthesize very complicated assembly addressing modes from complex C data types / pointer expressions.  systemtap or gdb
	      may not be able to parse some valid but complicated expressions.	Reference to such parameters from within systemtap can	result	in
	      "SDT asm not understood" errors.

       overly restrictive constraint
	      GCC  might  not be able to even compile the original program with the default "nor" constraint due to shortage of registers or other
	      reasons.	A compile-time gcc error such as "asm operand has impossible constraints" may result.

       There are two general workarounds to this family of problems.

       change the constraints
	      While compiling the original instrumented program, set the STAP_SDT_ARG_CONSTRAINT macro to different constraint strings.   See  the
	      GCC  manual  about  various options.  For example, on many machine architectures, "r" forces operands into registers, and "g" leaves
	      operands essentially unconstrained.

       revert to debuginfo
	      As long as the instrumented program compiles, it may be fine simply to keep using <sys/sdt.h> but eschew extraction of a	few  indi-
	      vidual  parameters.   In	the  worst  case, disable <sys/sdt.h> macros entirely to eschew the compiled-in instrumentation.  If DWARF
	      debuginfo was generated and preserved, a systemtap script could refer to the underlying source  context  variables  instead  of  the
	      positional STAP_PROBE parameters.

SEE ALSO

       stap(1),
       stapprobes(3stap),
       error::dwarf(7stap),
       http://gcc.gnu.org/onlinedocs/gcc/Constraints.html,
       http://sourceware.org/systemtap/wiki/UserSpaceProbeImplementation,
       error::reporting(7stap)

																 ERROR::SDT(7stap)