Sponsored Content
Full Discussion: Systemtap
Top Forums Programming Systemtap Post 302571018 by jim mcnamara on Saturday 5th of November 2011 01:35:17 PM
Old 11-05-2011
edit a file: put the stap -r '.....' command in file, let's call it mystap.sh stap prints to stdout. So:

Code:
chmod +x mystp.sh  # you only need to execute this one time

./stap.sh > outputfile

Is this what you meant?
Code:
stap -o myoutputfile  ' stap code here ...'

also does what you want, in this case it writes to myoutputfil.
 

We Also Found This Discussion For You

1. Programming

systemtap returntimeofday_s and some questions

Hi gurus, could you please explain few questions about systemtap. 1st === seems gettimeofday_s() always returns 0 stap -ve 'probe timer.s(4){ printf("%d ", gettimeofday_s()) }' returns 0 0 0 ... also gettimeofday_ms gettimeofday_ns When I am trying to investigate what is going on... (2 Replies)
Discussion started by: wakatana
2 Replies
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)
All times are GMT -4. The time now is 09:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy