| 1 |
.\" -*- nroff -*- |
| 2 |
.TH STAP\-MERGE 1 |
| 3 |
.SH NAME |
| 4 |
stap\-merge \- systemtap per-cpu binary merger |
| 5 |
|
| 6 |
.\" macros |
| 7 |
.\" do not nest SAMPLEs |
| 8 |
.de SAMPLE |
| 9 |
.br |
| 10 |
|
| 11 |
.nr oldin \\n(.i |
| 12 |
.RS |
| 13 |
.nf |
| 14 |
.nh |
| 15 |
.. |
| 16 |
.de ESAMPLE |
| 17 |
.hy |
| 18 |
.fi |
| 19 |
.RE |
| 20 |
.in \\n[oldin]u |
| 21 |
|
| 22 |
.. |
| 23 |
|
| 24 |
.SH SYNOPSIS |
| 25 |
|
| 26 |
.br |
| 27 |
.B stap\-merge |
| 28 |
[ |
| 29 |
.I OPTIONS |
| 30 |
] |
| 31 |
[ |
| 32 |
.I INPUT FILENAMES |
| 33 |
] |
| 34 |
|
| 35 |
.SH DESCRIPTION |
| 36 |
|
| 37 |
The stap\-merge executable applies when the \-b option has been used |
| 38 |
while running a |
| 39 |
.IR stap |
| 40 |
script. The \-b option will generate files |
| 41 |
per\-cpu, based on the timestamp field. Then stap\-merge will |
| 42 |
merge and sort through the per-cpu files based on the timestamp |
| 43 |
field. |
| 44 |
|
| 45 |
.SH OPTIONS |
| 46 |
|
| 47 |
The systemtap merge executable supports the following options. |
| 48 |
.TP |
| 49 |
.B \-v |
| 50 |
Verbose mode, displays three extra fields per set of collected data. |
| 51 |
.SAMPLE |
| 52 |
.BR [cpu number, sequence number of data, the length of the data set] |
| 53 |
.ESAMPLE |
| 54 |
.TP |
| 55 |
.BI \-o " OUTPUT_FILENAME" |
| 56 |
|
| 57 |
Specify the name of the file you would like the output to be |
| 58 |
redirected into. If this option is not specified than the |
| 59 |
output will be pushed to standard out. |
| 60 |
|
| 61 |
.SH EXAMPLES |
| 62 |
.SAMPLE |
| 63 |
$ stap \-v \-b \-e 'probe syscall.open { printf("%s(%d) open\\n", |
| 64 |
execname(), pid()) }' |
| 65 |
|
| 66 |
.ESAMPLE |
| 67 |
|
| 68 |
This should result in several |
| 69 |
.I stpd_cpu |
| 70 |
files (each labled with a number |
| 71 |
representing which cpu the file was produced from). |
| 72 |
|
| 73 |
.SAMPLE |
| 74 |
$ stap\-merge \-v stpd_cpu0 stpd_cpu1 |
| 75 |
|
| 76 |
.ESAMPLE |
| 77 |
|
| 78 |
Running the stap\-merge program in the same directory as the stap |
| 79 |
script earlier in the example, will produce an ordered sequence of |
| 80 |
packets with the three part label for each set of data. This |
| 81 |
result will be pushed through the standard output. An output file |
| 82 |
could have been specified using the "\-o" option. |
| 83 |
|
| 84 |
.SH FILES |
| 85 |
|
| 86 |
.TP |
| 87 |
Important files and their corresponding paths can be located in the |
| 88 |
stappaths (7) manual page. |
| 89 |
|
| 90 |
.SH SEE ALSO |
| 91 |
.nh |
| 92 |
.nf |
| 93 |
.IR stapprobes (3stap), |
| 94 |
.IR stappaths (7), |
| 95 |
.IR staprun (8), |
| 96 |
.IR stapvars (3stap), |
| 97 |
.IR stapex (3stap), |
| 98 |
.IR stap\-server (8), |
| 99 |
.IR gdb (1) |
| 100 |
|
| 101 |
.SH BUGS |
| 102 |
Use the Bugzilla link of the project web page or our mailing list. |
| 103 |
.nh |
| 104 |
.BR http://sourceware.org/systemtap/ , <[email protected]> . |
| 105 |
.hy |