Date: Thu, 4 Jan 2001 23:52:06 -0500 (EST) From: Daniel Eischen <eischen@vigrid.com> To: The Hermit Hacker <scrappy@hub.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: using -pthread causes mcopidl to seg fault ... Message-ID: <Pine.SUN.3.91.1010104234846.27572A-100000@pcnet1.pcnet.com> In-Reply-To: <Pine.BSF.4.31.0101050025570.368-100000@thelab.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.1010104234846.27572A-100000>