From owner-freebsd-current Wed Aug 18 18:33:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id B932615926 for ; Wed, 18 Aug 1999 18:33:08 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id SAA17301; Wed, 18 Aug 1999 18:30:50 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199908190130.SAA17301@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein Cc: Joel Ray Holveck , Richard Cownie , Alex Zepeda , freebsd-current@FreeBSD.ORG, tich@par28.ma.ikos.com Subject: Re: SIGBUS [was Re: gdb] In-reply-to: Your message of "Wed, 18 Aug 1999 20:50:05 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Aug 1999 18:30:50 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 18 Aug 1999, Joel Ray Holveck wrote: > > > > (gdb) run > > > Starting program: /tmp/./sieve > > > Program received signal SIGBUS, Bus error. > > > > That reminds me. I thought that SIGBUS meant byte-alignment errors. > > What does it mean on FreeBSD/x86? > > Another possible source for SIGBUS should be generated when accessing > a mmap'd region past the end of a file. > 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 -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message