From owner-freebsd-current@FreeBSD.ORG Tue Oct 19 23:17:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82A4916A4CE for ; Tue, 19 Oct 2004 23:17:59 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DF1E43D53 for ; Tue, 19 Oct 2004 23:17:59 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8D5E35150F; Tue, 19 Oct 2004 16:18:15 -0700 (PDT) Date: Tue, 19 Oct 2004 16:18:15 -0700 From: Kris Kennaway To: Chris Hedley Message-ID: <20041019231815.GA7266@xor.obsecurity.org> References: <20041018202949.J866@teapot.cbhnet> <20041019160026.GB55255@xor.obsecurity.org> <20041019170446.B866@teapot.cbhnet> <20041019212009.GA93330@xor.obsecurity.org> <20041020001044.D866@teapot.cbhnet> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline In-Reply-To: <20041020001044.D866@teapot.cbhnet> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org cc: Kris Kennaway Subject: Re: Crash with new bind/host cmds on -CURRENT (poss. runq_remove?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 23:17:59 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 20, 2004 at 12:13:46AM +0100, Chris Hedley wrote: > 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. >=20 > Hmm, that's what I already did. The only exception was having to use=20 > "kgdb" instead of "gdb -k" (the latter complained that it didn't=20 > understand "-k" which is odd, as it used to work). I was a bit surprised= =20 > that it didn't print the syslog buffer when I started it, too. If you don't use the kernel.debug, you won't get the debugging symbols. Kris --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBdaC3Wry0BWjoQKURArn2AJ4+J5su0FnV4BxfrdiEPD/p3b07cACfa9Cg EPqWIPEvlJSadfpY8ruoQJU= =vIFQ -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR--