Date: Sun, 17 Dec 2000 13:21:44 -0500 (EST) From: Daniel Eischen <eischen@vigrid.com> To: H <H.Lambermont@chello.nl> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mozilla and 4.2-RELEASE Message-ID: <Pine.SUN.3.91.1001217131740.27545A-100000@pcnet1.pcnet.com> In-Reply-To: <20001217181521.A35032@moya.hans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 17 Dec 2000, H wrote: > Szilveszter Adam wrote: > > > A gdb(1) trace shows that the segfault is in the internal functions of > > nspr, so it is possibly not a C++ problem. Once the stack trace went > > as deep as libc_r, however. > > > > Since the Mozilla team has dropped all FreeBSD tinderboxes from their > > cluster (although they have added OpenBSD 2.5 back) they are probably > > totally unaware of the problems. > > Well, I complained about this in their nspr newsgroup: See the thread > news://news.mozilla.org/3A37A3DB.3E457946%40blender.nl > > It seems to boil down to "Fatal error 'siglongjmp()ing between thread > contexts is undefined by POSIX 1003.1'" in libc_r Ouch. _If_that_really_is_the_problem, then the developers ought to be taken out and shot! I do find it hard to believe that someone would attempt to do that, so it might just be a symptom of the real problem. Perhaps signal masks aren't being properly set and the wrong thread is receiving the signal. -- Dan Eischen 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?Pine.SUN.3.91.1001217131740.27545A-100000>