Date: Thu, 27 May 2004 20:30:40 -0400 From: David Magda <dmagda@ee.ryerson.ca> To: Robert Watson <rwatson@freebsd.org> Cc: stable@freebsd.org Subject: Re: how to interpret crash? Message-ID: <3F18ECCE-B03E-11D8-A04B-000A95B96FF8@ee.ryerson.ca> In-Reply-To: <Pine.NEB.3.96L.1040527194447.74482A-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1040527194447.74482A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 27, 2004, at 19:55, Robert Watson wrote:
> you need. If you've cvsup'd and no longer have the source code for the
> old kernel, regardless of having debugging symbols, you're in a much
> worse
> starting point for tracking down the problem.
I don't pretend to have the knowledge to actually fix a kernel issue.
:> I would simply want to have a way to provide a useful backtrace for
developers. Even if I cvsup'd I could always use CVSWeb to look at the
previous revision.
> One important reason that the debugging kernel isn't kept around is
> space
> considerations: in -CURRENT, a 5mb kernel will generally be
> accompanied by
Yes, this is why I suggested a variable in make.conf with an .if
statement in the Makefiles.
Searching through the the Makefiles: around line 193 in file
sys/conf/kern.post.mk you have (from a 5.2.1-p7 system):
.if defined(DEBUG) && defined(INSTALL_DEBUG)
${INSTALL} -p -m 555 -o root -g wheel ${FULLKERNEL}
${DESTDIR}${KODIR}
.else
${INSTALL} -p -m 555 -o root -g wheel ${KERNEL_KO}
${DESTDIR}${KODIR}
.endif
Would changing it to the following work?
.if defined(DEBUG) && defined(INSTALL_DEBUG)
${INSTALL} -p -m 555 -o root -g wheel ${FULLKERNEL}
${DESTDIR}${KODIR}
.else
${INSTALL} -p -m 555 -o root -g wheel ${KERNEL_KO}
${DESTDIR}${KODIR}
.if defined(INST_KERNDEBUG)
${INSTALL} -p -m 555 -o root -g wheel ${FULLKERNEL}
${DESTDIR}${KODIR}
.endif
.endif
I haven't checked how FULLKERNEL is defined.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F18ECCE-B03E-11D8-A04B-000A95B96FF8>