Date: Wed, 20 Oct 2004 00:13:46 +0100 (BST) From: Chris Hedley <cbh-freebsd-current@groups.chrishedley.com> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-current@freebsd.org Subject: Re: Crash with new bind/host cmds on -CURRENT (poss. runq_remove?) Message-ID: <20041020001044.D866@teapot.cbhnet> In-Reply-To: <20041019212009.GA93330@xor.obsecurity.org> References: <20041018202949.J866@teapot.cbhnet> <20041019160026.GB55255@xor.obsecurity.org> <20041019212009.GA93330@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Oct 2004, Kris Kennaway wrote: > On Tue, Oct 19, 2004 at 05:06:46PM +0100, Chris Hedley wrote: >>> Unfortunately this doesn't seem to be useful - you should try to >>> obtain a debugging traceback. >> >> That can be arranged. Just pretend for a moment that I'm really dense and >> remind me how to go about creating one. ;) > > See the kernel debugging chapter in the developer's handbook. Hmm, that's what I already did. The only exception was having to use "kgdb" instead of "gdb -k" (the latter complained that it didn't understand "-k" which is odd, as it used to work). I was a bit surprised that it didn't print the syslog buffer when I started it, too. Chris.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041020001044.D866>