Date: Sun, 23 Apr 2000 18:25:28 +0200 From: Mark Huizer <freebsd@dohd.cx> To: Greg Lehey <grog@lemis.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Debugging kernel data Message-ID: <20000423182528.A58150@dohd.cx> In-Reply-To: <20000423114218.H4675@freebie.lemis.com>; from grog@lemis.com on Sun, Apr 23, 2000 at 11:42:18AM %2B0930 References: <20000413132050.D43342@dohd.cx> <20000423114218.H4675@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 23, 2000 at 11:42:18AM +0930, Greg Lehey wrote: > On Thursday, 13 April 2000 at 13:20:50 +0200, Mark Huizer wrote: > > Hi > > > > I'm trying to debug a kernel that is not crashing but hanging, with all > > processes in 'inode' wchan. So I did a 'call panic()', and now I have > > the crashdump, but is there a way to get to the data structures of the > > kernel??? > > Sure. What are you looking for? Have you read the section on kernel > debugging in the handbook? > Yep, done that kind of stuff before, but never on non-crashing kernels :-( Problem is I want to get at the stacks of various running processes, and the syscalls they are making. I started using the vinum gdb macros, which got me a bit further, though not yet enough, I'm afraid. Mark -- Nice testing in little China... 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?20000423182528.A58150>