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

Document Information

Preface

1.  About DTrace

2.  D Programming Language

3.  Aggregations

4.  Actions and Subroutines

Actions

Default Action

Data Recording Actions

trace

tracemem

printf

printa

stack

ustack

jstack

uaddr

usym

Destructive Actions

Process Destructive Actions

stop

raise

copyout

copyoutstr

system

Kernel Destructive Actions

breakpoint

panic

chill

Special Actions

Speculative Actions

exit

Subroutines

alloca

basename

bcopy

cleanpath

copyin

copyinstr

copyinto

dirname

inet_ntoa

inet_ntoa6

inet_ntop

msgdsize

msgsize

mutex_owned

mutex_owner

mutex_type_adaptive

progenyof

rand

rw_iswriter

rw_write_held

speculation

strjoin

strlen

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

16.  Postmortem Tracing

17.  Performance Considerations

18.  Stability

19.  Translators

20.  Versioning

Index

Special Actions

This section describes actions that are neither data recording actions nor destructive actions.

Speculative Actions

The actions associated with speculative tracing are speculate, commit, and discard. These actions are discussed in Chapter 7, Speculative Tracing.

exit

void exit(int status)

The exit action is used to immediately stop tracing, and to inform the DTrace consumer that it should cease tracing, perform any final processing, and call exit(3C) with the status specified. Because exit returns a status to user-level, it is a data recording action, However, unlike other data storing actions, exit cannot be speculatively traced. exit will cause the DTrace consumer to exit regardless of buffer policy. Because exit is a data recording action, it can be dropped.

When exit is called, only DTrace actions already in progress on other CPUs will be completed. No new actions will occur on any CPU. The only exception to this rule is the processing of the END probe, which will be called after the DTrace consumer has processed the exit action and indicated that tracing should stop.