Date: Wed, 3 Jan 2001 14:30:50 -0600 From: "Jim King" <jim@jimking.net> To: "Daniel Eischen" <eischen@vigrid.com> Cc: <stable@FreeBSD.ORG> Subject: Re: Threaded C++ Question Message-ID: <012701c075c4$13718360$524c8486@jking> References: <Pine.SUN.3.91.1010103151937.1588A-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Daniel Eischen" <eischen@vigrid.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?012701c075c4$13718360$524c8486>