JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Solaris Dynamic Tracing Guide
search filter icon
search icon

Document Information


1.  Introduction

2.  Types, Operators, and Expressions

3.  Variables

4.  D Program Structure

5.  Pointers and Arrays

6.  Strings

7.  Structs and Unions

8.  Type and Constant Definitions

9.  Aggregations

10.  Actions and Subroutines

11.  Buffers and Buffering

12.  Output Formatting

13.  Speculative Tracing

14.  dtrace(1M) Utility

15.  Scripting

16.  Options and Tunables

17.  dtrace Provider

18.  lockstat Provider

19.  profile Provider

20.  fbt Provider

21.  syscall Provider

22.  sdt Provider

23.  sysinfo Provider

24.  vminfo Provider

25.  proc Provider

26.  sched Provider

27.  io Provider

28.  mib Provider

29.  fpuinfo Provider

30.  pid Provider

31.  plockstat Provider

32.  fasttrap Provider

33.  User Process Tracing

34.  Statically Defined Tracing for User Applications

35.  Security

36.  Anonymous Tracing

37.  Postmortem Tracing

38.  Performance Considerations

39.  Stability

40.  Translators

41.  Versioning





A behavior implemented by the DTrace framework that can be performed at probe firing time that either traces data or modifies system state external to DTrace. Actions include tracing data, stopping processes, and capturing stack traces, among others.


An object that stores the result of an aggregating function as defined formally in Chapter 9, Aggregations, indexed by a tuple of expressions that can be used to organize the results.


A D program declaration consisting of a probe specifier list, an optional predicate, and an optional list of action statements surrounded by braces { }.


A program that uses DTrace to enable instrumentation and reads out the resulting stream of trace data. The dtrace command is the canonical DTrace consumer; the lockstat(1M) utility is another specialized DTrace consumer.


A dynamic tracing facility that provides concise answers to arbitrary questions.


A group of enabled probes and their associated predicates and actions.


A logical expression that determines whether or not a set of tracing actions should be executed when a probe fires. Each D program clause may have a predicate associated with it, surrounded by slashes / /.


A location or activity in the system to which DTrace can dynamically bind instrumentation including a predicate and actions. Each probe is named by a tuple indicating its provider, module, function, and semantic name. A probe may be anchored to a particular module and function, or it may be unanchored if it is not associated with a particular program location (for example, a profile timer).


A kernel module that implements a particular type of instrumentation on behalf of the DTrace framework. The provider exports a namespace of probes and a stability matrix for its name and data semantics, as shown in the chapters of this book.


A behavior implemented by the DTrace framework that can be performed at probe firing time that modifies internal DTrace state but does not trace any data. Similar to actions, subroutines are requested using the D function call syntax.


A collection of D assignment statements that convert implementation details of a particular instrumented subsystem into a object of struct type that forms an interface of greater stability than the input expression.