1 .TH sh_pidcolors.d 1m "$Date:: 2007-10-03 #$" "USER COMMANDS"
3 sh_pidcolors.d - Demonstration of deeper DTrace Bourne shell analysis.
8 This extends sh_syscolors.d by including some "pid" provider tracing
9 as a starting point for deeper analysis. Currently it adds the probes,
11 pid$target:a.out:e*:entry,
12 pid$target:a.out:e*:return
14 which means, all functions from the /usr/bin/sh binary that begin with
15 the letter "e". This adds about 34 probes. Customise it to whichever
16 parts of /usr/bin/sh or the system libraries you are interested in.
18 The filename for syscalls may be printed as the shell name, if the
19 script was invoked using the form "shell filename" rather than running
20 the script with an interpreter line.
24 Evolving - uses the DTrace Shell provider, which may change
25 as additional features are introduced. Check Shell/Readme
26 to see what version these scripts are based on.
42 Elapsed time from previous line to this line
45 Filename of the shell script
48 Line number of filename
51 Type of call (func/builtin/cmd/line/shell)
54 Shell function, builtin or command name
56 Watch the first column carefully, it prints the CPU-id. If it
57 changes, then it is very likely that the output has been shuffled.
60 See the DTraceToolkit for further documentation under the
61 Examples, Notes and Docs directories. The example files may be
62 especially useful as they aim to demonstrate how to interpret
65 sh_pidcolors.d will run until Ctrl-C is hit.