From owner-freebsd-current Thu Jan 4 20:52:36 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 20:52:34 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 2399F37B400 for ; Thu, 4 Jan 2001 20:52:34 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id XAA27979; Thu, 4 Jan 2001 23:52:06 -0500 (EST) Date: Thu, 4 Jan 2001 23:52:06 -0500 (EST) From: Daniel Eischen To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: using -pthread causes mcopidl to seg fault ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 5 Jan 2001, The Hermit Hacker wrote: > > morning all ... > > running 5.0-CURRENT here, and found the other day that mcopidl > started to segfault the other day in kdelibs (from CVS) ... this evening, > someone brought up the possibility that its a threading issue, and > suggested taking -pthread out of the compile to see if it fixes it ... it > did. > > are there any known problems with -pthread in 5.0-CURRENT right > now? anything I can do to debug it (a gdb trace of the core file shows > zip) ... Yeah, threaded C++ apps that make use of libstdc++ are borken in both -current and -stable. See the stable mailing list and search for C++ and/or mozilla. You can probably get around the problem by explicitly linking with -lgcc_r. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message