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

[Brad Spencer <brad%anduin.eldar.org@localhost>]

Taylor R Campbell <riastradh%NetBSD.org@localhost> writes:

>> Date: Sat, 22 Jul 2023 07:46:28 -0400
>> From: Brad Spencer <brad%anduin.eldar.org@localhost>
>> 
>> After really making sure that the build directory for the custom kernel
>> was gone, the build with "-g" worked fine.  Sorry for the
>> noise... however, the original problem reported still is present, so
>> adding debugging symbols didn't seem to help.
>
> Can you please share the output of:
>
> ctfdump -t SAMWISE/netbsd
> ctfdump -t /netbsd
>
> after you have rebuilt and reinstalled the kernel from a clean build
> directory?

Those are here:

http://anduin.eldar.org/~brad/ctf/ctfdump_built_SAMWISE
http://anduin.eldar.org/~brad/ctf/ctfdump_booted_SAMWISE

Since this is a pure DOMU PV, the booted kernel lives on the DOM0 and
the ctfdump was taken from there using the path indicated in the DOMU
Xen config.  The two outputs appear to be identical.  I also placed the
kernel in /netbsd on the DOMU, although there really should not be
anything that cares much about that on a pure PV (and that didn't effect
dtrace).

> If you're not booting from /netbsd, run it on whatever is the kernel
> that you are actually booting -- and double-check to make sure that
> you are actually booting the kernel you think you are booting.

Yes, I did that double check.  I am running the kernel build with "-g"
as far as I can tell.  For completeness here is the "config -x" of the
booted kernel:

http://anduin.eldar.org/~brad/ctf/config_SAMWISE