Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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)

Check Out this Related Man Page

PMDASYSTEMTAP(1)					       Performance Co-Pilot						  PMDASYSTEMTAP(1)

NAME
pmdasystemtap - Systemtap performance metrics domain agent (PMDA) DESCRIPTION
pmdasystemtap is a Performance Metrics Domain Agent (PMDA) which exports metric values from the Linux Systemtap dynamic tracing toolkit. This implementation uses the stap(1) tool, which is a front-end to the Systemtap toolkit. INSTALLATION
In order to access performance data exported by Systemtap from with PCP, it is necessary to perform two configuration steps: 1. Configure Systemtap probes, and verify them with stap(1). These should be produced in a format that is easily parsed, and then stored in the $PCP_PMDAS_DIR/systemtap/probes.stp file. 2. Configure pmdasystemtap to extract the values from the text produced by stap. Two example probes are implemented in the default systemtap PMDA script - readdir and sync traces (see $PCP_PMDAS_DIR/systemtap/pmdasystemtap.pl for details). # cd $PCP_PMDAS_DIR/systemtap # [ edit probes.stp, test /usr/bin/stap probes.stp ] # [ edit pmdasystemtap.pl ] Once this is setup, you can access the names and values for the systemtap performance metrics by doing the following as root: # cd $PCP_PMDAS_DIR/systemtap # ./Install If you want to undo the installation, do the following as root: # cd $PCP_PMDAS_DIR/systemtap # ./Remove pmdasystemtap is launched by pmcd(1) and should never be executed directly. The Install and Remove scripts notify pmcd(1) when the agent is installed or removed. FILES
$PCP_PMDAS_DIR/systemtap/probes.stp probe configuration file for stap(1), run by pmdasystemtap $PCP_PMDAS_DIR/systemtap/Install installation script for the pmdasystemtap agent $PCP_PMDAS_DIR/systemtap/Remove undo installation script for the pmdasystemtap agent $PCP_LOG_DIR/pmcd/systemtap.log default log file for error messages from pmdasystemtap SEE ALSO
pmcd(1) and stap(1). 3.8.10 Performance Co-Pilot PMDASYSTEMTAP(1)
Man Page