From owner-freebsd-hackers Tue Sep 28 12:11:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phobos.illtel.denver.co.us (dsl-206.169.4.82.wenet.com [206.169.4.82]) by hub.freebsd.org (Postfix) with ESMTP id 8A32F14F9D for ; Tue, 28 Sep 1999 12:11:38 -0700 (PDT) (envelope-from abelits@phobos.illtel.denver.co.us) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.9.1a/8.6.9) with SMTP id MAA18477; Tue, 28 Sep 1999 12:10:49 -0700 Date: Tue, 28 Sep 1999 12:10:49 -0700 (PDT) From: Alex Belits To: "Darren R. Davis" Cc: Nate Williams , Scm486@aol.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Netscape Bus Error In-Reply-To: <37F0DC3D.7F4A969D@calderasystems.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Sep 1999, Darren R. Davis wrote: > I believe that a Bus Error is specifically referencing miss aligned data vs > segmentation violation > (SIGSEGV) which is accessing data that is either free'd or not yours, etc. > I always thought > it strange on an Intel processor, since this was more a 68K/RISC thing. > The only penalty on Intel > was taking many more cycles to complete. Of course I haven't looked that > deeply at what the > code handling for the bus error signal really detects. But, never the > less, it is still a Netscape bug. It's SIGSEGV in disguise -- netscape intercepts it and generates SIGBUS: ---8<--- abelits@es1840$ netscape& [1] 67114 abelits@es1840$ kill -SEGV 67114 abelits@es1840$ [1]+ Bus error netscape abelits@es1840$ --->8--- -- Alex ---------------------------------------------------------------------- Excellent.. now give users the option to cut your hair you hippie! -- Anonymous Coward To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message