From owner-freebsd-current@FreeBSD.ORG Tue Oct 19 16:00:12 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 E0C2316A4CE for ; Tue, 19 Oct 2004 16:00:12 +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 B872443D3F for ; Tue, 19 Oct 2004 16:00:12 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8CDF5522C7; Tue, 19 Oct 2004 09:00:26 -0700 (PDT) Date: Tue, 19 Oct 2004 09:00:26 -0700 From: Kris Kennaway To: Chris Hedley Message-ID: <20041019160026.GB55255@xor.obsecurity.org> References: <20041018202949.J866@teapot.cbhnet> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WYTEVAkct0FjGQmd" Content-Disposition: inline In-Reply-To: <20041018202949.J866@teapot.cbhnet> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org 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 16:00:13 -0000 --WYTEVAkct0FjGQmd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 18, 2004 at 08:45:30PM +0100, Chris Hedley wrote: > Hopefully I'm not covering old ground with this one, I had a quick look= =20 > through the list and couldn't find anything. I've been having a few=20 > problems with either bind9 or the programs which call it via localhost=20 > which cause the system to panic. I'm afraid I seem to have neglected the= =20 > debugging symbols, but the function stack is as follows: Unfortunately this doesn't seem to be useful - you should try to obtain a debugging traceback. Kris --WYTEVAkct0FjGQmd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBdToaWry0BWjoQKURAvBnAKDIH1V+r2EqlivTbfAzoii4/gcNAQCgsKeK +Kpgx9oCHZtoiCYTnHmGSco= =7tQW -----END PGP SIGNATURE----- --WYTEVAkct0FjGQmd--