Date: Wed, 3 Jan 2001 14:17:18 -0600 From: "Jim King" <jim@jimking.net> To: <stable@FreeBSD.ORG> Subject: Re: Threaded C++ Question Message-ID: <011601c075c2$2f956900$524c8486@jking> References: <20010102131012.A1922@superhero.org> <004101c07515$206f9340$04e48486@marble> <20010103103948.A62250@dragon.nuxi.com> <00e201c075be$8a500570$524c8486@jking>
next in thread | previous in thread | raw e-mail | index | archive | help
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! Now to take a shot at getting Mozilla 0.6 built and running... 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?011601c075c2$2f956900$524c8486>