From owner-freebsd-hackers Mon Feb 10 00:52:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA19595 for hackers-outgoing; Mon, 10 Feb 1997 00:52:52 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA19589 for ; Mon, 10 Feb 1997 00:52:48 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA11694; Mon, 10 Feb 1997 09:52:06 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id JAA18736; Mon, 10 Feb 1997 09:46:22 +0100 (MET) Message-ID: Date: Mon, 10 Feb 1997 09:46:22 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: cmott@srv.net (Charles Mott) Cc: freebsd-hackers@freebsd.org Subject: Re: Bus Errors References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Charles Mott on Feb 9, 1997 17:48:27 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Charles Mott wrote: > What does "Bus error" mean? UTSL :-) Various possible reasons. What quickly comes to mind are various access violations, like trying to do direct port IO from an unprivileged program, or messing up the (uh!) segment registers so you get a GPF. Also, there's something with access violations on a mapped region vs. touching unmapped memory, that is currently differentiated between SIGBUS vs. SIGSEGV. We've been recently discussing this (in -core) since it confuses our Linuxulator, and is also inconsisten with other systems. It's likely that somebody will be changed there in the future. I think an unaligned access on a 486+ with the AC flag set causes a SIGBUS, too. On the PDP-11, unaligned access and access to bus addresses that were not existent (and thus timed out in the bus controller) were the original reasons for a SIGBUS. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)