Date: Tue, 9 Nov 1999 10:39:38 -0500 From: Greg Lehey <grog@mojave.sitaranetworks.com> To: Zhihui Zhang <zzhang@cs.binghamton.edu>, freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic Message-ID: <19991109103938.63558@mojave.sitaranetworks.com> In-Reply-To: <Pine.GSO.3.96.991109084025.9832B-100000@sol.cs.binghamton.edu>; from Zhihui Zhang on Tue, Nov 09, 1999 at 08:52:58AM -0500 References: <Pine.GSO.3.96.991109084025.9832B-100000@sol.cs.binghamton.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 9 November 1999 at 8:52:58 -0500, Zhihui Zhang wrote: > > I have set up an environment of remote serial debugging on FreeBSD > 3.3-Release. I have a program that whenever it runs the kernel panics. > Is there any way I can use remote serial debugging to trace this panic > process instead of examining a dead kernel (i.e., coredump)? Yes. > Or, is there any way I can use to drop the debugged kernel to debugger > mode whenever it runs a certain piece of code? Yes. That's what breakpoints are for. If you set a breakpoint on panic, you'll go into the debugger. But you don't need that, since you go into the debugger on panic anyway. If you're expecting a breakpoint or panic, and you want to do it in gdb as opposed to ddb, set gdb mode ahead of time. This is also useful for debugging ddb :-) Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991109103938.63558>