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

ERROR::PASS2(7stap)													       ERROR::PASS2(7stap)

NAME

       error::pass2 - systemtap pass-2 errors

DESCRIPTION

       Errors that occur during pass 2 (elaboration) can have a variety of causes.  Common types include:

       unavailable probe point classes
	      Some  types  of  probe  points are only available on certain system versions, architectures, and configurations.	For example, user-
	      space process.*  probes may require utrace or uprobes capability in the kernel for this architecture.

       unavailable probe points
	      Some probe points may be individually unavailable even when their class is fine.	For example, kprobe.function("foobar") may fail if
	      function	foobar	does  not  exist  in  the  kernel any more.  Debugging or symbol data may be absent for some types of .function or
	      .statement probes; check for availability of debuginfo.  Try the stap-prep program to download possibly-required debuginfo.   Use  a
	      wildcard	parameter  such as stap -l 'kprobe.function("*foo*")' to locate still-existing variants.  Use ! or ?  probe point suffixes
	      to denote optional / preferred-alternatives, to let the working parts of a script continue.

       typos  There might be a spelling error in the probe point name ("sycsall" vs.  "syscall").  Wildcard probes may not find a match at all	in
	      the  tapsets.   Recheck the names using stap -l PROBEPOINT.  Another common mistake is to use the .  operator instead of the correct
	      -> when dereferencing context variable subfields or pointers: $foo->bar->baz even if in C one would say foo->bar.baz.

       unavailable context variables
	      Systemtap scripts often wish to refer to variables from the context of the probed programs using $variable  notation.   These  vari-
	      ables may not always be available, depending on versions of the compiler, debugging/optimization flags used, architecture, etc.  Use
	      stap -L PROBEPOINT to list available context variables for given probes.	Use the @defined() expression to test for the  resolvabil-
	      ity  of  a context variable expression.  Consider using the stap --skip-badvars option to silently replace misbehaving context vari-
	      able expressions with zero.

GATHERING MORE INFORMATION

       Increasing the verbosity of pass-2 with an option such as --vp 02 can help pinpoint the problem.

SEE ALSO

       stap(1),
       stap-prep(1),
       stapprobes(3stap),
       probe::*(3stap),
       error::dwarf(7stap),
       error::inode-uprobes(7stap),
       warning::debuginfo(7stap),
       error::reporting(7stap)

															       ERROR::PASS2(7stap)

ERROR::PASS5(7stap)													       ERROR::PASS5(7stap)

NAME

       error::pass5 - systemtap pass-5 errors

DESCRIPTION

       Errors that occur during pass 5 (execution) can have a variety of causes.

       exceptional events during script execution
	      The  systemtap  translator  and runtime include numerous error checks that aim to protect the systems and the users from mistakes or
	      transient conditions.  The script may deliberately call the error() tapset function to signal a problem.	 Some  memory  needed  for
	      accessing  $context  variables  may  be temporarily unavailable.	Consider using the try/catch construct to wrap script fragments in
	      exception-handling code.	Consider using the stap --suppress-handler-errors or stap --skip-badvars option.

       resource exhaustion
	      One of several types of space or time resource limits may be exceeded by the script, including system overload, too many	tuples	to
	      be  stored  in  an  array, etc.  Some of the error messages identify the constraint by macro name, which may be individually raised.
	      Consider using the stap --suppress-handler-errors option.  Extend or disable resource limits using the stap -DLIMIT=NNNN option.

       remote execution server problems
	      If you use the stap --remote option to direct a systemtap script to be executed somewhere else, ensure that an SSH connection may be
	      made to the remote host, and that it has the current systemtap runtime installed & available.

       installation/permission problems
	      It  is possible that your installation of systemtap was not correctly installed.	For example, the /usr/bin/staprun program may lack
	      the necessary setuid permissions, or your invoking userid might not have sufficient privileges (root, or stapusr and  related  group
	      memberships).  Environment variables may interfere with locating /usr/libexec/.../stapio.

       errors from target program
	      The program invoked by the stap -c CMD option may exit with a non-zero code.

       uncaught exceptions in the target program
	      When  using --runtime=dyninst you may encounter an issue where the target program aborts with a message like "terminate called after
	      throwing an instance of 'foo_exception'".  This is unfortunately a limitation of Dyninst, which sometimes prevents  exceptions  from
	      properly unwinding through instrumented code.

GATHERING MORE INFORMATION

       Increasing the verbosity of pass-5 with an option such as --vp 00001 can help pinpoint the problem.

SEE ALSO

       stap(1),
       http://sourceware.org/systemtap/wiki/TipExhaustedResourceErrors,
       error::fault(7stap),
       error::reporting(7stap)

															       ERROR::PASS5(7stap)