strace-log-merge(1) [freebsd man page]
STRACE-LOG-MERGE(1) General Commands Manual STRACE-LOG-MERGE(1) NAME
strace-log-merge - merge strace -ff -tt output SYNOPSIS
strace-log-merge STRACE_LOG strace-log-merge --help DESCRIPTION
strace-log-merge merges the output of strace -ff -tt[t] command, prepending PID to each line and sorting the result using time stamp as a key. OPTIONS
--help Show program usage and exit. STRACE_LOG Output file name prefix of files produced by a strace -ff -tt[t] command. EXIT STATUS
0 Success Non-zero Error occurred: either no argument specified (in that case a usage is printed), or something went wrong during the processing of STRACE_LOG.* files. USAGE EXAMPLE
$ strace -o sleepy -ff -tt -e trace=execve,nanosleep sh -c 'sleep 0.1 & sleep 0.2 & sleep 0.3' $ strace-log-merge sleepy | fold -w 72 -s 13475 21:13:52.040837 execve("/bin/sh", ["sh", "-c", "sleep 0.1 & sleep 0.2 & sleep 0."...], 0x7ffde54b2450 /* 33 vars */) = 0 13478 21:13:52.044050 execve("/bin/sleep", ["sleep", "0.3"], 0x5631be4f87a8 /* 33 vars */) = 0 13476 21:13:52.044269 execve("/bin/sleep", ["sleep", "0.1"], 0x5631be4f87a8 /* 33 vars */) = 0 13477 21:13:52.044389 execve("/bin/sleep", ["sleep", "0.2"], 0x5631be4f87a8 /* 33 vars */) = 0 13478 21:13:52.046207 nanosleep({tv_sec=0, tv_nsec=300000000}, NULL) = 0 13476 21:13:52.046303 nanosleep({tv_sec=0, tv_nsec=100000000}, NULL) = 0 13477 21:13:52.046318 nanosleep({tv_sec=0, tv_nsec=200000000}, NULL) = 0 13476 21:13:52.146852 +++ exited with 0 +++ 13475 21:13:52.146942 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=13476, si_uid=1000, si_status=0, si_utime=0, si_stime=0} --- 13477 21:13:52.247782 +++ exited with 0 +++ 13475 21:13:52.247885 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=13477, si_uid=1000, si_status=0, si_utime=0, si_stime=0} --- 13478 21:13:52.347680 +++ exited with 0 +++ 13475 21:13:52.347786 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=13478, si_uid=1000, si_status=0, si_utime=0, si_stime=0} --- 13475 21:13:52.348069 +++ exited with 0 +++ NOTES
strace-log-merge does not work well with strace logs generated by strace -tt invocation that pass midnight, as those lack the information required for the proper sorting. Employing the -ttt option in the respective strace invocation should solve the problem. BUGS
strace-log-merge does not perform any checks whether the files specified are in the correct format and implies that only files from a sin- gle strace session match STRACE_LOG.* glob pattern. HISTORY
The initial version of strace-log-merge was written by Denys Vlasenko in 2012. REPORTING BUGS
Problems with strace-log-merge should be reported to the strace mailing list at <strace-devel@lists.sourceforge.net>. SEE ALSO
strace(1) strace UNKNOWN 2018-04-11 STRACE-LOG-MERGE(1)
Check Out this Related Man Page
strace(8) System Manager's Manual strace(8) NAME
strace - Writes STREAMS event trace messages to standard output SYNOPSIS
/usr/sbin/strace [mod_ID sub_ID pri_level] DESCRIPTION
The strace command gets STREAMS event trace messages from STREAMS drivers and modules via the STREAMS log driver (strlog), and writes these messages to standard output. You can limit the messages strace receives by specifying arguments to the command. The arguments, which must be specified together, are the following: Specifies the STREAMS module identification number. Specifies a subidentification number (often corresponding to a minor device). Specifies a tracing priority level. The strace command will get messages of a level equal to or less than the value in the pri_level argument. The value of the argument must be a nonnegative integer. You can specify all as the value for any of the arguments in the strace command line. The value all indicates that there are no restric- tions for that argument. You can also specify multiple sets of the command's three arguments to obtain the messages from more than one driver or module. More than one strace process can open the STREAMS log driver at a time. When you invoke strace, the log driver compares the sets of argu- ments from the command line with actual trace messages, returning the messages that satisfy the criteria. STREAMS event trace messages have the following format: seqnum stdtime tickstime pri_level ntfycode mod_ID sub_ID msgtext where: The event trace sequence number. The time the message was sent, in the format hh:mm:ss. The time the message was sent, measured in machine ticks since the last boot. The tracing priority level as defined by the STREAMS driver or module that originates the messages. Can be either of the following indicators: Indicates that the message has also been saved in the error log. Indicates that the message signaled a fatal error. The module identification number of the trace message source. The subidentification number of the trace message source. The trace message text. The strace command runs until terminated by the user. NOTES
Running strace with several sets of arguments can negatively affect STREAMS performance, particularly for those modules and drivers sending the messages. Also be aware that strace may not be able to handle a large number of messages. If drivers and modules return messages to strace too quickly, some may be lost. EXAMPLES
To display all trace messages received from the driver or module identified by mod_ID 28, enter: strace 28 all all To display those trace messages from the driver or module identified by mod_ID 28 and its minor devices identified by the sub_IDs 2, 3, and 4, enter: strace 28 2 all 28 3 all 28 4 all This command line causes messages of any tracing priority level to be displayed. To display the trace messages from the same driver or module and sub_IDs, but limited to certain priority levels, enter: strace 28 2 0 28 3 0 28 4 1 This command line specifies that messages from driver or module 28 and sub_IDs 2 and 3 must have a tracing priority of 0, and those from sub_ID 4 must have a tracing priority equal to or less than 1. RELATED INFORMATION
Commands: strclean(8), strerr(8). Interfaces: strlog(7). delim off strace(8)