From owner-freebsd-hackers Sun Apr 23 9:25:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from eeyore.local.dohd.cx (d0030.dtk.chello.nl [213.46.0.30]) by hub.freebsd.org (Postfix) with ESMTP id D4F0437B5DB for ; Sun, 23 Apr 2000 09:25:45 -0700 (PDT) (envelope-from freebsd@dohd.cx) Received: from tiggr.local.dohd.cx (tiggr.local.dohd.cx [::ffff:10.0.0.10]) by eeyore.local.dohd.cx (Postfix+IPv6) with ESMTP id 9A118BAB3; Sun, 23 Apr 2000 18:25:29 +0200 (MET DST) Received: by tiggr.local.dohd.cx (Postfix, from userid 1008) id BDA235D45; Sun, 23 Apr 2000 18:25:28 +0200 (CEST) Date: Sun, 23 Apr 2000 18:25:28 +0200 From: Mark Huizer To: Greg Lehey Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Debugging kernel data Message-ID: <20000423182528.A58150@dohd.cx> References: <20000413132050.D43342@dohd.cx> <20000423114218.H4675@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.4i In-Reply-To: <20000423114218.H4675@freebie.lemis.com>; from grog@lemis.com on Sun, Apr 23, 2000 at 11:42:18AM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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