[DTrace-devel] [oracle/dtrace-utils] 3a0909: pid: Support probe names specifying offsets

[euloh]

  Branch: refs/heads/devel
  Home:   https://github.com/oracle/dtrace-utils
  Commit: 3a09091a3d6795b5b936a676c7b3aaae424eb07b
      https://github.com/oracle/dtrace-utils/commit/3a09091a3d6795b5b936a676c7b3aaae424eb07b
  Author: Eugene Loh <eugene.loh at oracle.com>
  Date:   2024-02-01 (Thu, 01 Feb 2024)

  Changed paths:
    M Makeconfig
    M dtrace.spec
    M include/dtrace/pid.h
    M libcommon/uprobes.c
    M libdtrace/Build
    M libdtrace/dt_pid.c
    M libdtrace/dt_prov_uprobe.c
    M test/unittest/pid/tst.emptystack.d
    M test/unittest/pid/tst.float.d
    A test/unittest/pid/tst.offsets.r
    A test/unittest/pid/tst.offsets.sh
    M test/unittest/pid/tst.probefunc.d

  Log Message:
  -----------
  pid: Support probe names specifying offsets

In DTrace, a pid-provider probe name can be "entry" or "return".
The probe name can also specify offsets, including wildcards (globs).

Add support for "offset" probes.

Note that offset used for the pid probe name is different from that used
for the underlying uprobe.  So introduce a new field pps_nameoff that
allows us to track both offsets.

Also, the "float" trigger when launched with "before" timing will
presumably never fire the entry or return probes.  So, tst.emptystack.d
ought perhaps to be split into a entry/return test and an offset test.

Signed-off-by: Eugene Loh <eugene.loh at oracle.com>
Reviewed-by: Kris Van Hees <kris.van.hees at oracle.com>