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

Document Information


1.  About DTrace

2.  D Programming Language

3.  Aggregations

4.  Actions and Subroutines

5.  Buffers and Buffering

6.  Output Formatting

7.  Speculative Tracing

8.  dtrace(1M) Utility

9.  Scripting

10.  Options and Tunables

11.  Providers

12.  User Process Tracing

13.  Statically Defined Tracing for User Applications

14.  Security

15.  Anonymous Tracing

Anonymous Enablings

Claiming Anonymous State

Anonymous Tracing Examples

16.  Postmortem Tracing

17.  Performance Considerations

18.  Stability

19.  Translators

20.  Versioning

Anonymous Enablings

To create an anonymous enabling, use the -A option with a dtrace(1M) invocation that specifies the desired probes, predicates, actions and options. dtrace will add a series of driver properties representing your request to the dtrace(7D) driver's configuration file, typically /kernel/drv/dtrace.conf. These properties will be read by the dtrace(7D) driver when it is loaded. The driver will enable the specified probes with the specified actions, and create an anonymous state to associate with the new enabling. Normally, the dtrace(7D) driver is loaded on-demand, as are any drivers that act as DTrace providers. To allow tracing during boot, the dtrace(7D) driver must be loaded as early as possible. dtrace adds the necessary forceload statements to /etc/system (see system(4)) for each required DTrace provider and for dtrace(7D) itself.

Thereafter, when the system boots, a message is emitted by dtrace(7D) to indicate that the configuration file has been successfully processed.

All options may be set with an anonymous enabling, including buffer size, dynamic variable size, speculation size, number of speculations, and so on.

To remove an anonymous enabling, specify -A to dtrace without any probe descriptions.