From owner-freebsd-gnome Sat Jan 26 12:28:50 2002 Delivered-To: freebsd-gnome@freebsd.org Received: from creme-brulee.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id D013A37B402; Sat, 26 Jan 2002 12:28:46 -0800 (PST) Received: from shumai.marcuscom.com (marcus@shumai.marcuscom.com [192.168.1.4]) by creme-brulee.marcuscom.com (8.11.6/8.11.6) with ESMTP id g0QKRIZ00578; Sat, 26 Jan 2002 15:27:18 -0500 (EST) (envelope-from marcus@marcuscom.com) Subject: Re: Bus errors in Galeon after upgrading GNOME bits From: Joe Clarke To: Maxim Sobolev Cc: freebsd-gnome@FreeBSD.ORG 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> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.1 Date: 26 Jan 2002 15:28:51 -0500 Message-Id: <1012076931.99280.18.camel@shumai.marcuscom.com> Mime-Version: 1.0 Sender: owner-freebsd-gnome@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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