From owner-freebsd-stable@FreeBSD.ORG Thu May 27 17:31:07 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 783BE16A4CE; Thu, 27 May 2004 17:31:07 -0700 (PDT) Received: from tomts10-srv.bellnexxia.net (tomts10.bellnexxia.net [209.226.175.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7A8F43D45; Thu, 27 May 2004 17:31:06 -0700 (PDT) (envelope-from dmagda@ee.ryerson.ca) Received: from number6.magda.ca ([67.68.49.151]) by tomts10-srv.bellnexxia.netESMTP <20040528003024.FXEZ24047.tomts10-srv.bellnexxia.net@number6.magda.ca>; Thu, 27 May 2004 20:30:24 -0400 Received: from [192.168.1.132] (gandalf.magda.ca [192.168.1.132]) by number6.magda.ca (8.12.11/8.12.11) with ESMTP id i4S0UOKw000258; Thu, 27 May 2004 20:30:25 -0400 (EDT) (envelope-from dmagda@ee.ryerson.ca) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <3F18ECCE-B03E-11D8-A04B-000A95B96FF8@ee.ryerson.ca> Content-Transfer-Encoding: 7bit From: David Magda Date: Thu, 27 May 2004 20:30:40 -0400 To: Robert Watson X-Mailer: Apple Mail (2.613) cc: stable@freebsd.org Subject: Re: how to interpret crash? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Magda List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 May 2004 00:31:07 -0000 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.