Table of Contents
- 4.1 Action Functions
- 4.2 Subroutine Functions
- 4.2.1 alloca
- 4.2.2 basename
- 4.2.3 bcopy
- 4.2.4 cleanpath
- 4.2.5 copyin
- 4.2.6 copyinstr
- 4.2.7 copyinto
- 4.2.8 d_path
- 4.2.9 dirname
- 4.2.10 getmajor
- 4.2.11 getminor
- 4.2.12 htonl
- 4.2.13 htonll
- 4.2.14 htons
- 4.2.15 index
- 4.2.16 inet_ntoa
- 4.2.17 inet_ntoa6
- 4.2.18 inet_ntop
- 4.2.19 lltostr
- 4.2.20 mutex_owned
- 4.2.21 mutex_owner
- 4.2.22 mutex_type_adaptive
- 4.2.23 mutex_type_spin
- 4.2.24 ntohl
- 4.2.25 ntohll
- 4.2.26 ntohs
- 4.2.27 progenyof
- 4.2.28 rand
- 4.2.29 rindex
- 4.2.30 rw_iswriter
- 4.2.31 rw_read_held
- 4.2.32 rw_write_held
- 4.2.33 speculation
- 4.2.34 strchr
- 4.2.35 strjoin
- 4.2.36 strlen
- 4.2.37 strrchr
- 4.2.38 strstr
- 4.2.39 strtok
- 4.2.40 substr
You use D function calls such as trace and
printf to invoke two different kinds of
services that are provided by DTrace: actions
and subroutines. Actions trace data or modify
a state that is external to DTrace, while
subroutines affect only the internal DTrace
state.
This chapter defines DTrace actions and subroutines and also describes their syntax and semantics.