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

ERROR::PASS1(7stap)													       ERROR::PASS1(7stap)

NAME

       error::pass1 - systemtap pass-1 errors

DESCRIPTION

       Errors  that occur during pass 1 (parsing) usually mean a basic syntax error of some sort occurred in the systemtap script.  There are sev-
       eral classes of problems possible:

       plain syntax error
	      The systemtap script parser detects a large variety of errors, such as missing operands, bad punctuation.  It  tries  to	list  what
	      kinds  of  tokens  it was expecting to see, and will show the region of the source code with the problem.  Please review the stap(1)
	      man page and/or the tutorial, to correct the script's syntax.

       grammar ambiguities
	      There is at least one known ambiguity in the systemtap grammar.  It relates to the optionality of ; (semicolon)  separators  between
	      statements, and the ++ and -- increment/decrement operators.  If the parser indicates an error, consider adding some explicit ; sep-
	      arators between nearby statements and try again.

       missing command line arguments
	      A systemtap script that uses the $N and @N constructs for substituting in command-line options may fail if not enough  options  were
	      given on the stap command line.

       compatibility changes
	      Some  versions  of systemtap have changed the language incompatibly, for example by adding the try/catch keywords for exception han-
	      dling.  In such cases, rerun systemtap with the --compatibility=VERSION option, substituting the last systemtap version  where  your
	      script was known to work.  You may also check the release-history NEWS file for compatibility changes.

GATHERING MORE INFORMATION

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

SEE ALSO

       stap(1),
       error::reporting(7stap)

															       ERROR::PASS1(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)