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

Document Information

Preface

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

Actions

Default Action

Data Recording Actions

trace()

tracemem()

printf()

printa()

stack()

ustack()

jstack()

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()

msgdsize()

msgsize()

mutex_owned()

mutex_owner()

mutex_type_adaptive()

progenyof()

rand()

rw_iswriter()

rw_write_held()

speculation()

strjoin()

strlen()

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

Glossary

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 13, 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.