Date: Thu, 26 Apr 2001 06:26:20 -0700 From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca> To: "Jaime Kikpole" <jkikpole@cairodurham.org> Cc: "Kris Kennaway" <kris@obsecurity.org>, freebsd-stable@FreeBSD.ORG Subject: Re: Random (?) kernel panics Message-ID: <200104261326.f3QDQwR53296@cwsys.cwsent.com> In-Reply-To: Your message of "Thu, 26 Apr 2001 11:58:54 -0000." <20010426115855.0D87137B423@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20010426115855.0D87137B423@hub.freebsd.org>, "Jaime Kikpole" writes : > Kris Kennaway <kris@obsecurity.org> said: > > On Wed, Apr 25, 2001 at 09:42:45PM -0400, Jaime Kikpole wrote: > > > makeoptions DEBUG=-g #Build kernel with gdb(1) debug > symbols > > > > The debugging stuff is all stripped out when the kernel is installed > > into /, however it remains in the kernel.debug file in your kernel > > build directory: if you haven't rebuilt your kernel since, you can use > > this kernel with gdb and the vmcore image (it must be the same one as > > the kernel which panicked and dumped the vmcore, otherwise it won't > > work properly). > > So I'll need to reboot to the kernel.debug kernel, wait for the next > panic, and then I'll have the details in gdb. Right? No. You only use the debug kernel for its symbols. The handbook says: Now, after a crash dump, go to /sys/compile/WHATEVER and run gdb -k. From gdb do: symbol-file kernel.debug exec-file /var/crash/kernel.0 core-file /var/crash/vmcore.0 and voila, you can debug the crash dump using the kernel sources just like you can for any other program. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104261326.f3QDQwR53296>