stap-report(1) [centos man page]

STAP-REPORT(1)						      General Commands Manual						    STAP-REPORT(1)

NAME

       stap-report - collect system information that is useful for debugging systemtap bugs

SYNOPSIS

       stap-report

DESCRIPTION

       The  stap-report  executable  collects  system information that is useful for debugging systemtap bugs. It is a good idea to include such a
       report in bug reports especially if you send them directly to the upstream. stap-report can be run either as a normal user or as root.  The
       report will be more complete if stap-report is run as root.

EXAMPLES

	      $ stap-report > report.txt
	      $ head report.txt
	      == id ==
	      uid=1000(user) gid=1000(user) groups=122(stapdev),123(stapusr),129(stapsys)
	      == stap -V ==
	      Systemtap translator/driver (version 2.2.1/0.153, Debian version 2.2.1-1)
	      Copyright (C) 2005-2013 Red Hat, Inc. and others
	      This is free software; see the source for copying conditions.
	      enabled features: AVAHI LIBSQLITE3 NSS TR1_UNORDERED_MAP NLS
	      == which stap ==
	      /usr/bin/stap
	      == locate --regex '/stap(run)?$' | xargs ls -ald ==

SEE ALSO

       stap(1)

BUGS

       Use the Bugzilla link of the project web page or our mailing list.  http://sourceware.org/systemtap/,<systemtap@sourceware.org>.

																    STAP-REPORT(1)

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)