From owner-freebsd-current Thu Aug 19 9: 9:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B261C15024 for ; Thu, 19 Aug 1999 09:09:46 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA25954; Thu, 19 Aug 1999 09:09:17 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA18406; Thu, 19 Aug 1999 09:09:16 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 19 Aug 1999 09:09:16 -0700 (PDT) Message-Id: <199908191609.JAA18406@vashon.polstra.com> To: hasty@rah.star-gate.com Subject: Re: SIGBUS [was Re: gdb] In-Reply-To: <199908190130.SAA17301@rah.star-gate.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199908190130.SAA17301@rah.star-gate.com>, Amancio Hasty wrote: > > On 18 Aug 1999, Joel Ray Holveck wrote: > > > > > That reminds me. I thought that SIGBUS meant byte-alignment errors. > > > What does it mean on FreeBSD/x86? > > The boehm garbage collector is trying to find the memory limit so I guess > in FreeBSD is going to get a SIGBUS. > > In linux they get SIGV Right. FreeBSD gives SIGBUS for pages that are mapped but protected, and SIGSEGV for pages that aren't mapped at all. As I recall, Linux doesn't even have SIGBUS as far as the kernel is concerned. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message