From owner-freebsd-stable Mon Apr 15 4:21:33 2002 Delivered-To: freebsd-stable@freebsd.org Received: from van-laarhoven.org (ap-z-5ab8.adsl.wanadoo.nl [212.129.218.184]) by hub.freebsd.org (Postfix) with SMTP id 408B537B400 for ; Mon, 15 Apr 2002 04:21:29 -0700 (PDT) Received: (qmail 58736 invoked from network); 15 Apr 2002 11:21:28 -0000 Received: from heather.van-laarhoven.org (10.66.0.2) by uitsmijter.van-laarhoven.org with SMTP; 15 Apr 2002 11:21:28 -0000 Date: Mon, 15 Apr 2002 13:21:28 +0200 (CEST) From: Nick Hibma To: Rasputin Cc: "stable@freebsd.org" Subject: Re: Status, USB/Olympus E-10 In-Reply-To: <20020415120458.B3160@shikima.mine.nu> Message-ID: <20020415131815.C36693-100000@heather.van-laarhoven.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Running with a debug kernel should be no problem and not much slower > > than running with a production kernel. > > I thought the '-g' flag created two kernels, > kernel and kernel.debug. > > I've always found I can run with kernel, then just pass kernel.debug to > 'gdb -k' after a panic/reboot (see below). That requires you to set up a dumpdev as well as compiling a debugging kernel. But, yes, kernel.debug corresponds to /boot/kernel/kernel. As a side note: If you get the panic PC you can do a gdb -k /sys/i386/KERNELNAME/kernel.debug dis 0xADDRESS and get the disassembly and program listing of the address where things went wrong. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message