[DTrace-devel] [oracle/dtrace-utils] 27894c: pid: ensure pid offset probes perform lookup with ...

[Kris Van Hees]

  Branch: refs/heads/devel
  Home:   https://github.com/oracle/dtrace-utils
  Commit: 27894c5d08a32b6167511069217a5ce138933281
      https://github.com/oracle/dtrace-utils/commit/27894c5d08a32b6167511069217a5ce138933281
  Author: Kris Van Hees <kris.van.hees at oracle.com>
  Date:   2026-02-10 (Tue, 10 Feb 2026)

  Changed paths:
    M include/sys/sol_procfs.h
    M libdtrace/dt_pid.c
    M libproc/Psymtab.c

  Log Message:
  -----------
  pid: ensure pid offset probes perform lookup with adjusted address

For PIE executables and libraries, pid offset probes need to have the
address adjusted based on the actual segment load address.

Signed-off-by: Kris Van Hees <kris.van.hees at oracle.com>
Reviewed-by: Nick Alcock <nick.alcock at oracle.com>


  Commit: d1708bc4a9a274ea870a3582283aca121706da37
      https://github.com/oracle/dtrace-utils/commit/d1708bc4a9a274ea870a3582283aca121706da37
  Author: Kris Van Hees <kris.van.hees at oracle.com>
  Date:   2026-02-10 (Tue, 10 Feb 2026)

  Changed paths:
    M test/unittest/pid/tst.dash.sh

  Log Message:
  -----------
  test: make tst.dash.sh work for position-independent code

When code is compiled as position-independent code, the logic for
comparing the reported PC at probe firing needs to adjust for the
fact that the reported addresses are absolute whereas the addresses
obtained from the executable are relative to the mapping base

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


  Commit: 37f073bcfa170d8aa6191b690af89a86426b0f94
      https://github.com/oracle/dtrace-utils/commit/37f073bcfa170d8aa6191b690af89a86426b0f94
  Author: Kris Van Hees <kris.van.hees at oracle.com>
  Date:   2026-02-10 (Tue, 10 Feb 2026)

  Changed paths:
    M test/unittest/usdt/tst.pidprobes.sh

  Log Message:
  -----------
  test: adjust tst.pidprobes.sh to account for PIE executables

When the test executable is compiled as position independent code,
the comparison with expected results fails unless the reported PC
values are adjusted based on the actual load address.  This is safe
to do in general, because for non-PIE cases the adjustment will be
0.

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


  Commit: e85c438752ab9d49f6407798cfd8cf31c319fcb9
      https://github.com/oracle/dtrace-utils/commit/e85c438752ab9d49f6407798cfd8cf31c319fcb9
  Author: Kris Van Hees <kris.van.hees at oracle.com>
  Date:   2026-02-10 (Tue, 10 Feb 2026)

  Changed paths:
    M dtrace.spec
    R test/unittest/arrays/tst.ctf-dynsized-bounds-runtime.d
    A test/unittest/arrays/tst.ctf-dynsized-bounds-runtime.sh

  Log Message:
  -----------
  test: account for member name change in mm_struct

The flexible array at the end of the mm_struct has changed name in newer
kernels.  Rather than depending on a particular name, we can simply get
the name of the last member (since that is there the flexible array is
always found) and try to use that.

The testsuite gains a dependency on bpftool for this test.

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


Compare: https://github.com/oracle/dtrace-utils/compare/d7dd136fe7a0...e85c438752ab

To unsubscribe from these emails, change your notification settings at https://github.com/oracle/dtrace-utils/settings/notifications