Lines Matching +full:on +full:- +full:module
33 .Op Fl -libxo
46 .Op Fl m Oo Ar provider : Oc Ar module Oo Oo Ar predicate Oc Ar action Oc
47 .Op Fl f Oo Oo Ar provider : Oc Ar module : Oc Ar function Oo Oo Ar predicate \
49 .Op Fl n Oo Oo Oo Ar provider : Oc Ar module : Oc Ar function : Oc Ar name \
51 .Op Fl i Ar probe-id Oo Oo Ar predicate Oc Ar action Oc
62 .Bl -bullet -offset indent
67 specifiers (provider, module, function, name)
70 programs written directly on the command line
103 D program code specified on the command line must be appropriately quoted to
104 avoid interpretation of meta-characters by the shell.
107 .Bl -tag -width indent
115 forces the D compiler to compile a D program using the 32-bit data model.
120 forces the D compiler to compile a D program using the 64-bit data model.
125 D programs compiled for either data model can be executed on both 32-bit and
126 64-bit kernels.
164 attempts to reduce the buffer size or exit depending on the setting of the
172 option is present on the command line,
177 specified on the command line or using the
202 For example, if-statements in D are implemented using such transformations: a
203 conditional clause in a probe body is replaced at compile-time by a separate
204 probe predicated on the original condition.
231 .It Fl f Oo Oo Ar provider : Oc Ar module : Oc Ar function Oo Oo Ar predicate \
237 .Ar provider:module:function ,
238 .Ar module:function ,
253 option on the command line at a time.
257 .Ql -> .
259 .Ql <- .
311 .It Fl i Ar probe-id Op Oo Ar predicate Oc Ar action
313 .Ar ( probe-id )
317 You can specify probe IDs using decimal integers as shown by `dtrace -l`.
361 .It Fl -libxo
366 .It Fl m Oo Ar provider : Oc Ar module Oo Oo Ar predicate Oc Ar action Oc
367 Specify module name to trace or list
371 .Ar provider:module
373 .Ar module .
377 .Ar module
379 .Ar module
386 option can be specified on the command line at a time.
387 .It Fl n Oo Oo Oo Ar provider : Oc Ar module : Oc Ar function : Oc Ar name \
393 .Ar provider:module:function:name , module:function:name , function:name ,
408 option can be specified on the command line at a time.
415 .Fl -libxo
444 Grab the specified process-ID
449 option is present on the command line,
453 The first process-ID is made available to any D programs specified on the
463 The remaining probe description fields module, function, and name are left
470 option on the command line at a time.
579 .Bl -tag -width indent
589 Size of the per-CPU principal buffer.
595 Must be specified in number-per-second with the
599 Specifies the CPU on which to enable tracing.
621 Turn on flow indentation.
677 use regular human-readable output which is its default behavior.
723 .Bl -tag -width indent
769 ease re-use of settings from a C build environment.
775 .Bl -bullet -offset indent
783 __sparc (on SPARC systems only)
785 __sparcv9 (on SPARC systems only when 64-bit programs are compiled)
787 __i386 (on x86 systems only when 32-bit programs are compiled)
789 __amd64 (on x86 systems only when 64-bit programs are compiled)
791 __`uname -s`_`uname -r` (for example,
792 .Ql FreeBSD_9.2-RELEASE .
815 option) or on the command line
825 The output will always have a top-level object called
830 output time rather than probe firing time, an identifier for the CPU on
832 .Bd -literal
841 "module": ...,
845 ... (script-specific output)
859 <module>...</module>
863 ... (script-specific output)
870 of the fields are empty (in this example, module and function values
872 .Bd -literal
877 <module/>
881 ... (script-specific output)
890 .Bd -literal
892 <div class="data" data-tag="timestamp">...</div>
894 <div class="data" data-tag="cpu">...</div>
896 <div class="data" data-tag="id">...</div>
898 <div class="data" data-tag="provider">...</div>
900 <div class="data" data-tag="module">...</div>
902 <div class="data" data-tag="function">...</div>
904 <div class="data" data-tag="name">...</div>
905 <div class="data" data-tag="... (script-specific output)">...</div>
914 and a data-tag is associated with each of the keys.
918 array's contents depend on the probes' actions and is explained below.
925 .Bd -literal
946 .Bd -literal
947 # dtrace --libxo json,pretty -n 'BEGIN { printf("... %Y, ..", walltimestamp); }'
975 .Dq aggregation-data
977 .Bd -literal
979 "aggregation-data": [
987 "aggregation-name": ...
1007 the left-hand side and the right-hand side of human-readable
1011 .Bd -literal
1013 "aggregation-data": [
1033 "aggregation-name": ...
1049 .Bd -literal
1065 .Bd -literal
1066 # dtrace -x oformat=json,pretty -On 'BEGIN { sym((uintptr_t)&`prison0); }'
1074 # dtrace --libxo json,pretty -On 'BEGIN { sym((uintptr_t)curthread); }'
1089 .Dq stack-frames
1093 .Dq ustack-frames .
1097 .Bd -literal
1099 "stack-frames": [
1102 "module": "dtrace.ko",
1108 "module": "dtrace.ko",
1117 "ustack-frames": [
1120 "module": "libc.so.7",
1126 "module": "libdtrace.so.2",
1140 .Bd -literal
1144 "object-name": "kernel",
1149 "member-name": "td_lock",
1162 .Dq type-identifier
1165 The fields generated will depend on the kind of error that was encountered
1170 provides a special pseudo-probe to represent drops.
1176 .Bd -literal
1178 "cpu": -1,
1179 "id": -1,
1181 "module": "INTERNAL",
1192 You can specify zero or more additional arguments on the
1197 option or on the command line.
1199 .Bl -tag -width /boot/dtrace.dof -compact
1205 .Bl -tag -width indent