Date: Tue, 14 Sep 1999 11:55:20 +0930 From: Greg Lehey <grog@lemis.com> To: greg <greg@jules.res.cmu.edu> Cc: hackers@FreeBSD.ORG Subject: Re: debugging a proc's kernel stack... Message-ID: <19990914115519.A10106@freebie.lemis.com> In-Reply-To: <199909132000.UAA11296@jules.res.cmu.edu>; from greg on Mon, Sep 13, 1999 at 08:00:02PM %2B0000 References: <199909132000.UAA11296@jules.res.cmu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, 13 September 1999 at 20:00:02 +0000, greg wrote: > Hi, I want to see where some a deadlock is occurring in the kernel. I've got > a dump with a bunch of processes in the inode or namecache state. > > Can anybody give me a hint about how to find a proc's "kernel stack" - so that > I can find out what these kernel was doing for these processes when it locked > up... > > (see "repeated deadlocks in FS ..." on the smp list for more info about the problem)... Take a look at the .gdbinits in /usr/src/sys/modules/vinum. There's a little bit of documentation in vinum(4), but not really enough. The functions you might want are (extracted from gdb's "help user"): btp -- Show a backtrace for the process whose pid is specified as a parameter btpa -- Show backtraces for all processes in the system btpp -- Show a backtrace for the process previously selected with 'defproc' btr -- Show a backtrace from the ebp address specified defproc -- Specify a process for btpp and fr commands fr -- Show the frame of the stack of the process previously selected with 'defproc' Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key 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?19990914115519.A10106>