From owner-freebsd-questions Tue Jun 24 23:57:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA05962 for questions-outgoing; Tue, 24 Jun 1997 23:57:42 -0700 (PDT) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA05954 for ; Tue, 24 Jun 1997 23:57:32 -0700 (PDT) Received: (from smap@localhost) by gatekeeper.barcode.co.il (8.8.5/8.6.12) id JAA14021; Wed, 25 Jun 1997 09:56:31 +0300 (IDT) X-Authentication-Warning: gatekeeper.barcode.co.il: smap set sender to using -f Received: from localhost.barcode.co.il(127.0.0.1) by gatekeeper.barcode.co.il via smap (V1.3) id sma014015; Wed Jun 25 09:56:11 1997 Message-ID: <33B0C0C4.5E66@barcode.co.il> Date: Wed, 25 Jun 1997 09:55:00 +0300 From: Nadav Eiron X-Mailer: Mozilla 3.0 (X11; I; SunOS 5.5 sun4m) MIME-Version: 1.0 To: Brad Hendrickse CC: freebsd-questions@FreeBSD.ORG Subject: Re: Netscape 4.0b5 and XFree86 3.3 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brad Hendrickse wrote: > > Hi there, I was just wondering whether anyone else has come across this: > > I find that Netscape 4.0b5 crashes with a signal 11 error message. > AFAIK, that means bad RAM or CPU or something. I know my hardware isn't > bad, it survived a coupl of "make worlds" a few days ago, but I've had > this problem wth Netscape for a while now. Is it a known problem with > Netscape, or is it my hardware? > > TIA > > --brad I'm a FreeBSD user-- > > Fortune: > Of all the words of witch's doom > There's none so bad as which and whom. > The man who kills both which and whom > Will be enshrined in our Who's Whom. > -- Fletcher Knebel A signal 11 can also be the result of a bug in teh software. If there's just one piece of software that gives you signal 11s, then it's probably that software's fault and not the hardware. Also, taking into account te fact that it's Netscape, and a beta prerelease, I'd say this is simply a bug :-( Nadav