port-xen/57535: dtrace on Xen DOMU might need -x nolibs

[brad%anduin.eldar.org@localhost]

>Number:         57535
>Category:       port-xen
>Synopsis:       dtrace on Xen DOMU might need -x nolibs
>Confidential:   no
>Severity:       non-critical
>Priority:       high
>Responsible:    port-xen-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jul 21 16:45:00 +0000 2023
>Originator:     brad%anduin.eldar.org@localhost
>Release:        NetBSD 10.99.6
>Organization:
	eldar.org
>Environment:
System:	NetBSD samwise.nat.eldar.org 10.99.6 NetBSD 10.99.6 (SAMWISE) #0: Thu Jul 20 21:14:18 EDT 2023  brad%samwise.nat.eldar.org@localhost:/usr/src/sys/arch/amd64/compile/SAMWISE amd64
Architecture: x86_64
Machine: amd64
>Description:
	I was asked to run the following dtrace probe to help track down another problem:

dtrace -n 'sdt:xen:clock:, sdt:xen:hardclock:, sdt:xen:timecounter: { printf("%d %d %d %d %d %d %d %d", arg0, arg1, arg2, arg3, arg4, arg5, arg6, arg7) }'

This errors with:

dtrace: invalid probe specifier sdt:xen:clock:, sdt:xen:hardclock:, sdt:xen:timecounter: { printf("%d %d %d %d %d %d %d %d", arg0, arg1, arg2, arg3, arg4, arg5, arg6, arg7) }: "/usr/lib/dtrace/psinfo.d", line 46: syntax error near "u_int"

The workaround is to use '-x nolibs' on the dtrace command line.

>How-To-Repeat:
	Set up a -current DOMU in normal PV mode and try the probe mentioned
	above.  You may have to compile a kernel with KDTRACE_HOOKS.

>Fix:
	I know little about how dtrace works and can not offer a solution.
	However, I can probably test any proposed solution that might
	come around.