From owner-freebsd-current@FreeBSD.ORG Fri Aug 1 14:34:32 2003 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 2650137B401; Fri, 1 Aug 2003 14:34:32 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-63-207-60-135.dsl.lsan03.pacbell.net [63.207.60.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C19643FB1; Fri, 1 Aug 2003 14:34:31 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 71F9B66D7A; Fri, 1 Aug 2003 14:34:28 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 59D1252A; Fri, 1 Aug 2003 14:34:28 -0700 (PDT) Date: Fri, 1 Aug 2003 14:34:28 -0700 From: Kris Kennaway To: Steve Ames Message-ID: <20030801213428.GA22042@rot13.obsecurity.org> References: <200308011608.h71G85fo023429@energistic.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw" Content-Disposition: inline In-Reply-To: <200308011608.h71G85fo023429@energistic.com> User-Agent: Mutt/1.4.1i cc: arved@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: ports/news/newscache gives sig11 on recent -CURRENT 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: Fri, 01 Aug 2003 21:34:32 -0000 --wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 01, 2003 at 11:08:05AM -0500, Steve Ames wrote: >=20 > ports/news/newscache now gives me a sig11. It didn't a few weeks ago > but I really can't pin it down any closer than that. I thought it may > have been related to the new gcc import but I'm not able to check > that. After it gave me the sig11 I recompiled it and its dependancies > and that didn't fix anything. Can you try to get a gdb backtrace and track down the cause of the problem? Kris --wac7ysb48OaltWcw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/KtzkWry0BWjoQKURAiZ7AKCAXkaCZpbwqs9eBOw3rfmTQQz4UgCfaYZj 512kvA2mdb2+DYe3rH22o8Y= =Tkb3 -----END PGP SIGNATURE----- --wac7ysb48OaltWcw--