From owner-freebsd-stable Wed Jan 3 12:31: 5 2001 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 3 12:31:02 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id 55F2B37B400 for ; Wed, 3 Jan 2001 12:30:58 -0800 (PST) Received: from jking (jking.lgc.com [134.132.76.82]) by cgi.sstar.com (8.11.1/8.11.1) with SMTP id f03KUoE20929 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Wed, 3 Jan 2001 14:30:56 -0600 (CST) (envelope-from jim@jimking.net) Message-ID: <012701c075c4$13718360$524c8486@jking> From: "Jim King" To: "Daniel Eischen" Cc: References: Subject: Re: Threaded C++ Question Date: Wed, 3 Jan 2001 14:30:50 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel Eischen" wrote: > On Wed, 3 Jan 2001, Jim King wrote: > > Jim King wrote: > > > > > David O'Brien wrote: > > > > > > > On Tue, Jan 02, 2001 at 05:38:33PM -0600, Jim King wrote: > > > > > I'd like to know too. I plan on tackling Mozilla this weekend; it > > would > > > be > > > > > nice if it was a no-brainer. :-) > > > > > > > > I was unable to get our mozilla port to segfault with with or without > > the > > > > patch I'm planning on committing. > > > > > > > > It would be quite helpful if people could explain how to experience the > > > > problem. > > > > > > As of a couple weeks ago Mozilla M18 running on several flavors of 4.2 > > > (RELEASE and a couple different -stable's) would segfault immediately on > > > startup every time. This happened when I built it using the port, and > > when > > > I used the binary from mozilla.org. I haven't tried it since then, due to > > > the messages here about unresolved library bugs being the cause of the > > > problem. > > > > otoh... On a 4.2-stable built yesterday and a freshly-built gtk12 port, the > > Mozilla M18 binary from mozilla.org runs fine. Cool! > > That's because they changed the mozilla port to work around the > problem with libgcc (I believe with an explicit link -lgcc_r). > This should be reverted once the correct fix is committed to > libgcc and friends. But I didn't build Mozilla from the port, I downloaded the binary from mozilla.org. Something in -stable must have changed since the last time I tried to run the binary from mozilla.org. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message