Skip site navigation (1)Skip section navigation (2)
Date:      26 Jan 2002 15:28:51 -0500
From:      Joe Clarke <marcus@marcuscom.com>
To:        Maxim Sobolev <sobomax@FreeBSD.ORG>
Cc:        freebsd-gnome@FreeBSD.ORG
Subject:   Re: Bus errors in Galeon after upgrading GNOME bits
Message-ID:  <1012076931.99280.18.camel@shumai.marcuscom.com>
In-Reply-To: <1012034619.237.8.camel@notebook>
References:  <200201241550.g0OFoFb44084@vega.vega.com>  <1012003014.17563.7.camel@shumai.marcuscom.com>  <1012004355.17563.26.camel@shumai.marcuscom.com>  <1012034619.237.8.camel@notebook>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2002-01-26 at 03:43, Maxim Sobolev wrote:
> On Sat, 2002-01-26 at 02:19, Joe Clarke wrote:
> > On Fri, 2002-01-25 at 18:56, Joe Clarke wrote:
> > > On Thu, 2002-01-24 at 10:50, Maxim Sobolev wrote:
> > > > 
> > > > I've just rebuilt all pieces on my 4-STABLE scratchbox - galeon works like
> > > > a charm. Please let me know if you will have some more debugging info.
> > > 
> > > I rebuilt everything (GNOME, the whole works), and the problem
> > > persists.  I'm going to investigate further since I think libc might be
> > > linked in somewhere it shouldn't be.  I also get a similar crash when
> > > using FreshPort's search function.  Surprisingly, all the other GNOME
> > > apps seem to be working well.
> > 
> > Okay, more update.  _Any_ button I push results in the _same_ bus error
> > in libcrypto.  Downgrading to gnomevfs-1.0.3 fixed the problem. 
> > Upgrading to 1.0.4_1 re-introduces the problem.  It's not with libc, but
> > rather something in libcrypto.  Seems I have a mission this weekend.
> 
> I've identified the problem and committed a workaround. The root of the
> problem was that in gnomevfs-1.0.4 I had fixed detection of OpenSSL
> library, which resulted in gnomevfs being linked with it. The problem is
> that MD2_Update() function in libcrypto isn't stateless, so that when
> both mozilla and gnomevfs are using it at the same time it leads to a
> segfault. Perhaps gnomevfs developers should be notified about the
> problem, because it's unlikely that it is a FreeBSD-specific. Right now,
> please upgrade to gnomevfs-1.0.4_2.

That did it!  You saved me some digging.  I knew it had to be related to
re-entrancy since it was very similar to what I found in gnomedb. 
Thanks a lot, Maxim.

Joe

> 
> Thanks!
> 
> -Maxim



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-gnome" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1012076931.99280.18.camel>