stap-merge(1) [debian man page]
STAP-MERGE(1) General Commands Manual STAP-MERGE(1) NAME
stap-merge - systemtap per-cpu binary merger SYNOPSIS
stap-merge [ OPTIONS ] [ INPUT FILENAMES ] DESCRIPTION
The stap-merge executable applies when the -b option has been used while running a stap script. The -b option will generate files per-cpu, based on the timestamp field. Then stap-merge will merge and sort through the per-cpu files based on the timestamp field. OPTIONS
The systemtap merge executable supports the following options. -v Verbose mode, displays three extra fields per set of collected data. [cpunumber,sequencenumberofdata,thelengthofthedataset] -o OUTPUT_FILENAME Specify the name of the file you would like the output to be redirected into. If this option is not specified than the output will be pushed to standard out. EXAMPLES
$ stap -v -b -e 'probe syscall.open { printf("%s(%d) open ", execname(), pid()) }' This should result in several stpd_cpu files (each labled with a number representing which cpu the file was produced from). $ stap-merge -v stpd_cpu0 stpd_cpu1 Running the stap-merge program in the same directory as the stap script earlier in the example, will produce an ordered sequence of packets with the three part label for each set of data. This result will be pushed through the standard output. An output file could have been specified using the "-o" option. FILES
Important files and their corresponding paths can be located in the stappaths(7) manual page. SEE ALSO
stapprobes(3stap), stapfuncs(3stap), stappaths(7), staprun(8), stapvars(3stap), stapex(3stap), stap-server(8), gdb(1) BUGS
Use the Bugzilla link of the project web page or our mailing list. http://sourceware.org/systemtap/,<systemtap@sourceware.org>. STAP-MERGE(1)
Check Out this Related Man Page
STAP(7) Miscellaneous Information Manual STAP(7) NAME
stappaths - systemtap miscellaneous and paths DESCRIPTION
This manual page was generated on 2013-05-14 for systemtap 1.7. The following section will list the main paths in systemtap that are important to know and may be required to reference. Tapset Path: /usr/share/systemtap/tapset/ Systemtap data directory for cached systemtap files, unless overridden by the SYSTEMTAP_TAPSET environment variable or the XDG_DATA_DIRS environment variable. This directory stores a set of builtin functions and probe point aliases are provided by the scripts installed here. These are described in the stapfuncs(3stap) and stapprobes(3stap) manual pages. Runtime Path: /usr/share/systemtap/runtime/ The runtime sources, unless overridden by the SYSTEMTAP_RUNTIME environment variable. Staprun Path: /usr/bin/staprun The auxiliary program supervising module loading, interaction, and unloading. Stapio Path: /usr/lib/systemtap/stapio The Systemtap module input and output handler. sdt.h Path: /usr/include/sys/sdt.h Kernel debuginfo Path: /usr/lib/debug/lib/modules/$(uname -r)/ The location of kernel debugging information when packaged into the kernel-debuginfo RPM, unless overridden by the SYSTEMTAP_DEBUG- INFO_PATH environment variable. The default value for this variable is +:.debug:/usr/lib/debug:build and can be changed using $env SYSTEMTAP_DEBUGINFO_PATH=/path/to/vmlinux . Elfutils searches vmlinux in this path and it interprets the path as a base directory of which various subdirectories will be searched for finding modules. By default, systemtap will also look for vmlinux in these locations: /boot/vmlinux-`uname -r` /lib/modules/`uname -r`/vmlinux /lib/modules/`uname -r`/vmlinux.debug /lib/modules/`uname -r`/build/vmlinux /lib/modules/`uname -r`/.debug/vmlinux.debug /usr/lib/debug/lib/modules/`uname -r`/vmlinux.debug /var/cache/abrt-di/usr/debug/lib/modules/`uname -r`/ /var/cache/abrt-di/usr/lib/debug/lib/modules/`uname -r`/vmlinux.debug Debuginfo for user-space applications have source files located in /usr/src/debug/ Further file information on user-space applica- tions can be determined per-basis using rpm -ql <package>-debuginfo. For supported user-space applications information please visit the systemtap wiki. $HOME/.systemtap Systemtap data directory for cached systemtap files, unless overridden by the SYSTEMTAP_DIR environment variable. /tmp/stapXXXXXX Temporary directory for systemtap files, including translated C code and kernel object. /lib/modules/VERSION/build The location of kernel module building infrastructure. /usr/share/doc/systemtap*/examples Examples with greater detail, can be found here. Each example comes with a .txt or .meta file explaining what the example, sample or demo does and how it is ordinarily run. $SYSTEMTAP_DIR/ssl/server User's server-side SSL certificate database. If SYSTEMTAP_DIR is not set, the default is $HOME/.systemtap. $SYSTEMTAP_DIR/ssl/client User's private client-side SSL certificate database. If SYSTEMTAP_DIR is not set, the default is $HOME/.systemtap. /etc/systemtap/ssl/client Global client-side SSL certificate database. /etc/systemtap/staprun/ staprun's trusted signer certificate database. /etc/sysconfig/stap-server/ stap-server service global configuration file. /etc/stap-server/conf.d/*.conf stap-server service configuration files for default servers. /var/run/stap-server/ stap-server service default location of status files for running servers. /var/log/stap-server/log stap-server service default log file. FILES
/usr/share/systemtap/tapset SEE ALSO
stapprobes(3stap), stapfuncs(3stap), staprun(8), stapvars(3stap), stapex(3stap), stap-server(8), awk(1), gdb(1) BUGS
Use the Bugzilla link of the project web page or our mailing list. http://sourceware.org/systemtap/,<systemtap@sourceware.org>. Systemtap Team STAP(7)