From owner-freebsd-ports-bugs@FreeBSD.ORG Thu Aug 12 19:50:23 2004 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2183716A4CE for ; Thu, 12 Aug 2004 19:50:23 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16A5743D45 for ; Thu, 12 Aug 2004 19:50:23 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i7CJoMwt061399 for ; Thu, 12 Aug 2004 19:50:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i7CJoMl3061398; Thu, 12 Aug 2004 19:50:22 GMT (envelope-from gnats) Date: Thu, 12 Aug 2004 19:50:22 GMT Message-Id: <200408121950.i7CJoMl3061398@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: "Conrad J. Sabatier" Subject: Re: ports/70341: pan2 crashes when built with libgnuregex X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Conrad J. Sabatier" List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2004 19:50:23 -0000 The following reply was made to PR ports/70341; it has been noted by GNATS. From: "Conrad J. Sabatier" To: Joe Marcus Clarke Cc: pan@rebelbase.com, freebsd-gnats-submit@FreeBSD.org Subject: Re: ports/70341: pan2 crashes when built with libgnuregex Date: Thu, 12 Aug 2004 14:47:09 -0500 (CDT) On 12-Aug-2004 Conrad J. Sabatier wrote: > > On 12-Aug-2004 Joe Marcus Clarke wrote: >> Please provide a step-by-step example of how to reproduce this as >> well as a full backtrace with debugging symbols. I am not able to >> reproduce this with a simple regular expression custom filter. > > OK. First, I'm going to rebuild a few things with debugging support > enabled. Hmmm. After rebuilding the port and all of its dependencies, the problem seems to have gone away. Perhaps the fault was in another dependent package, or a system library (I also upgraded the world/kernel along with all of the packages). Hopefully, we won't be seeing this problem again. Sorry for the bogus report. :-) -- Conrad J. Sabatier -- "In Unix veritas"