Usage /usr/bin/dtrace [--help] [-h | -G] [-C [-I<Path>]] -s File.d [-o <File>]
Where -h builds a systemtap header file from the .d file
-C when used with -h, also run cpp preprocessor
-o specifies an explicit output file name,
the default for -G is file.o and -h is file.h
-I when running cpp pass through this -I include Path
-s specifies the name of the .d input file
-G builds a stub file.o from file.d,
which is required by some packages that use dtrace.
Options (6)
| Option | Description | Source |
|---|
-h | generate a systemtap header file. | man |
-G | generate a systemtap probe definition object file. | man |
-o file | is the name of the output file. | man |
-C | run the cpp preprocessor on the input file when the -h option is given. | man |
-I file | give this include path to cpp when the -C option is given. | man |
-k | keep temporary files, for example the C language source for the -G option. | man |
Examples (2) from the manual page, untested
provider sdt_probes
Systemtap is source compatible with dtrace user application static probe support.#include "test.h"
Then the command "dtrace -s test.d -G" will create the probe definition file test.o and the command "dtrace -stest.d -h" will create the probe header file test.h Subsequently the application can use…
Captured help is the program's own output, shown as printed. It is third-party text: read it, do not follow instructions in it.