euloh

We allocate space for dynamics variables, such as TLS variables, statically. Users have control over the space with the DTrace option dynvarsize. The size should be picked based on the...

For thread-local variables and associative arrays, the documentation says that unassigned variables are considered to be initialized to zero. Storage is not allocated until nonzero values are assigned. Storage is...

dt_cg_store_var() needs to copy terminating NUL byte for strings

1

Consider /* * Determine the amount of data to be copied. It is * the lesser of the size of the identifier and the * size of the data being...

Unrecognized PERF_RECORD_* causes "dtrace: processing aborted: Success"

1

When dt_consume_one() encounters an unrecognized hdr->type -- for example, PERF_RECORD_LOST -- it returns DTRACE_WORKSTATUS_ERROR without running dt_set_errno(dtp, errno). Then, dt_consume_cpu() passes DTRACE_WORKSTATUS_ERROR up the call stack through dtrace_consume() and dtrace_work()....

dtrace: could not enable tracing: BPF program load for '...' failed: No space left on device

2

A script like x = 1; @ = quantize(x); @ = quantize(x); [....97 similar lines...] @ = quantize(x); fails, printing about 16 Mbyte of BPF verifier log and ending in:...

Aggregations are not appropriately cleared

2

Consider: ``` BEGIN { @s = sum(1); printa(@s); printa(@s); printa(@s); exit(0) } ``` One sees the anticipated behavior -- "1" printed three times -- with DTv1. In contrast, with DTv2,...

Aggregations may be described in a D script but never used (e.g., probes using them never fire). In this case, the aggregations should not be reported. Consider ``` BEGIN {...

This type is obsolete. See discussion at https://oss.oracle.com/pipermail/dtrace-devel/2024-July/004975.html

conflicting version numbers

1

There are conflicting version numbers in DTrace. For example, libdtrace/dt_open.c const dt_version_t _dtrace_versions[] = { [...] DT_VERS_1_6_3, /* D API 1.6.3 */ DT_VERS_1_6_4, /* D API 1.6.4 */ DT_VERS_2_0, /*...