We are happy to announce the availability of the latest development version
of DTrace for Linux (2.0.0-1.12).
This new version is based on BPF and other Linux kernel tracing features and
is implemented entirely as a userspace application.
The functionality is not entirely on par with the kernel moduule based version
of DTrace for Linux (currently at version 1.2.1-1). Development continues in
an incremental fashion to make the full feature set of DTrace available using
existing kernel features.
WHERE TO FIND IT?
The new version of DTrace for Linux is available at:
https://github.com/oracle/dtrace-utils/tree/2.0-branch-dev
The main development branch for DTrace for Linux is at:
https://github.com/oracle/dtrace-utils/tree/dev
The most recent release tag is 2.0.0-1.12.
FEATURES
- Providers:
+ dtrace: BEGIN, END, and ERROR probes
+ fbt: Function Boundary Tracing (FBT) probes
+ sycall: System call entry and exit probes
+ profile: Timer-based profile-* and tick-* probes
+ sdt: Statically Defined Tracing (SDT) probes for kernel tracepoints
+ pid: Userspace function boundary tracing
+ usdt: Userspace Statically Defined Tracing (USDT) probes
+ [NEW] cpc: CPU Performacne Counter probes
+ [NEW] rawtp: SDT-style probes for kernel tracepoints with access to raw
(untranslated) tracepoint arguments
+ [NEW] proc: Process lifecycle related probes
- Aggregations:
+ Regular and indexed aggregations
+ Aggregation functions: avg, count, llquantize, lquantize, max, min,
quantize, stddev, and sum.
+ Aggregation actions: normalize, normalize, printa
+ [NEW] Aggregation action: clear
- Speculative tracing:
+ Functions: speculation, speculate, commit, and discard
- Variables:
+ Global variables
+ Thread-Local Storage (TLS) variables
+ Clause-local variables
+ Associative arrays for global and TLS variables
+ Built-in: arg0 - arg9, args[], caller, curcpu, curthread, epid, errno,
execname, gid, id, pid, ppid, probefunc, probemod, probename,
probeprov, stackdepth, tid, timestamp, ucaller, uid, ustackdepth,
walltimestamp
+ [NEW] Built-in: uregs[]
- Actions:
+ exit, freopen, ftruncate, mod, printa, printf, raise, setopt, stack,
sym, system, trace, uaddr, umod, ustack, usym
+ [NEW] tracemem
- Subroutines:
+ alloca, basename, bcopy, copyin, copyinstr, copyinto, dirname,
getmajor, getminor, htonl, htonll, htons, index, inet_ntoa, lltostr,
mutex_owned, mutex_owner, mutex_type_adaptive, mutex_type_spin, ntohl,
ntohll, ntohs, progenyof, rand, rindex, rw_iswriter, rw_read_held,
rw_write_held, strchr, strjoin, strlen, strrchr, strstr, strtok, substr
+ [NEW] copyout, copyoutstr
- BPF support:
+ Direct compilation of D source code into BPF programs.
+ Efficient use of pre-compiled BPF functions for library functions.
+ A bpflog option to request the BPF verifier log for loaded programs.
+ BPF program linking of dynamically generated code and pre-compiled
code to facilitate code sharing and code re-use.
+ Improved integrated disassembler for generated BPF code at the clause
and program level (-S in combination with the new -xdisasm=# option).
+ Improved trace data buffer handling based on memory mapped perf event
ring-buffers.
- Development and debugging:
+ Support to run dtrace under valgrind.
DEPENDENCIES
DTrace for Linux depends on libctf (part of newer binutils) -or-
libdtrace-ctf. While libctf is preferred, building against libdtrace-ctf is
fully supported. It can be found at:
https://github.com/oracle/libdtrace-ctf
DTrace for Linux makes use of BPF library functions that are compiled at
build time. It depends on BPF support in GCC and binutils to generate the
pre-compiled BPF function library.
DTrace for Linux makes use of 3 additional features that are not commonly
available in the Linux kernel:
- CTF data generation at compile time: this provides important datatype
information for kernel and kernel module symbols.
- waitfd() system call: this provides a mechanism to monitor for state
changes of processes that are being traced.
- /proc/kallsyms module grouping support: this adds annotation with module
names to all symbols that are part of a kernel module even if the module
is configured to be compiled into the kernel proper. This allows for
consistent ways to refer to probes by module and function (or probe) name.
These additional support features for tracing are available at:
https://github.com/oracle/dtrace-linux-kernel/tree/v2/6.1.8
Please consider joining our development list: dtrace-devel at oss.oracle.com
Enjoy!
|