From owner-freebsd-stable Wed Jan 3 5:55:57 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 05:55:54 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id F0CC337B402 for ; Wed, 3 Jan 2001 05:55:52 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.11.1/8.11.1) with ESMTP id f03DtLa95126; Wed, 3 Jan 2001 19:55:23 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 3 Jan 2001 19:55:21 +0600 (NS) From: Max Khon To: Erich Zigler Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Threaded C++ Question In-Reply-To: <20010102175034.B43962@superhero.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! > > > In reading through the archives I have seen several emails regarding the > > > problems people have experienced with MySQL, and Mozilla on 4.2 systems. I > > > was wondering if these problems have been resolved in the main source tree > > > yet. > > I'd like to know too. I plan on tackling Mozilla this weekend; it would be > > nice if it was a no-brainer. :-) > > To my knowledge they modified the Mozilla port to work around it. But I am > in the process of porting several C++ apps that are exhibiting truely > strange behavior. And I was wondering if this could be the cause. no fixes has been committed to main source tree so far. David O'Brien posted one workaround for this problem to -stable about two weeks ago. That patch has one problem described here: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21983 I have made another patch available at http://iclub.nsu.ru/~fjoe/libgcc-patch This patch should solve problems with threaded C++ programs and does not break fixes for PR/21983 Your feedback is appreciated (does it work for you or not, does it break backwards compatibility for you or not etc.) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message