From owner-freebsd-stable@FreeBSD.ORG Tue May 31 15:21:14 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C376216A41C for ; Tue, 31 May 2005 15:21:14 +0000 (GMT) (envelope-from bcasavan@tdkt.org) Received: from yeppers.tdkt.org (skyline.tdkt.org [209.98.211.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63BD743D53 for ; Tue, 31 May 2005 15:21:12 +0000 (GMT) (envelope-from bcasavan@tdkt.org) Received: from chenjesu.americas.sgi.com (cfcafwp.sgi.com [192.48.179.6]) (authenticated bits=0) by yeppers.tdkt.org (8.12.11/8.12.11/erikj-OpenBSD) with ESMTP id j4VFITL4015286; Tue, 31 May 2005 10:20:55 -0500 (CDT) Date: Tue, 31 May 2005 10:18:23 -0500 (CDT) From: Brent Casavant X-X-Sender: bcasavan@chenjesu.americas.sgi.com To: Benjamin Lutz In-Reply-To: <429A892C.6060006@datacomm.ch> Message-ID: <20050531101206.I1376@chenjesu.americas.sgi.com> References: <429A892C.6060006@datacomm.ch> Organization: "Angeltread Software Organization" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: libpthread problem (segfaults) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Brent Casavant List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 15:21:14 -0000 On Mon, 30 May 2005, Benjamin Lutz wrote: > I've run into an issue that has me stumped. Anything that I link against > libpthread on my FreeBSD-5.4-RELEASE/i386 installation will segfault as > soon as it tries making use of the threads. I may be hitting a manifestation of the same problem. With a freshly installed AbiWord (ports tree cvsup'd approximately 1 week after 5.4-RELEASE was announced, portupgrade performed) on a 5.4-RELEASE system, it crashes whenever the "Open" dialog is opened. The backtraces are next to useless, though there does seem to be a number of Pthreads calls in progress (pthread_mutexattr_init, pthread_testcancel, and pthread_timedwrlock). I'm casually debugging this problem as time permits, but to no avail thus far. Brent -- Brent Casavant Dance like everyone should www.angeltread.org be watching. KD5EMB, EN34lv