NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-xen/57535 (dtrace on Xen DOMU might need -x nolibs)
The following reply was made to PR port-xen/57535; it has been noted by GNATS.
From: Taylor R Campbell <riastradh%NetBSD.org@localhost>
To: Brad Spencer <brad%anduin.eldar.org@localhost>
Cc: gnats-bugs%netbsd.org@localhost, port-xen-maintainer%netbsd.org@localhost,
netbsd-bugs%netbsd.org@localhost, gnats-admin%netbsd.org@localhost
Subject: Re: port-xen/57535 (dtrace on Xen DOMU might need -x nolibs)
Date: Sat, 22 Jul 2023 11:12:37 +0000
> Date: Sat, 22 Jul 2023 06:42:27 -0400
> From: Brad Spencer <brad%anduin.eldar.org@localhost>
>
> I did a clean build of the world after a cvs update of the source tree
> and the problem mentioned in this PR is still present:
Can you please share the output of:
$ ctfdump -t SAMWISE/adiantum.o
$ ctfdump -t SAMWISE/netbsd
$ config -x SAMWISE/netbsd
in your clean build?
If you delete the SAMWISE build directory and rebuild it, do you get
the same output?
> I noted that a difference between GENERIC and XEN3_DOM0 is that there is
> a 'makeoptions DEBUG="-g"' present with a comment that it is needed for
> CTF and this option isn't present in XEN3_DOMU.
Evidently I never noticed this because I always build with MKDEBUG=yes
(or MKDEBUGKERNEL=yes) which renders it unnecessary.
I think maybe we should delete the makeoptions lines in the kernel
configs, and set MKDEBUG=yes or at least MKDEBUGKERNEL=yes by default.
Home |
Main Index |
Thread Index |
Old Index