Xref: utzoo comp.unix.questions:19813 comp.unix.wizards:20545
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!mips!apple!netcom!hue
From: hue@netcom.UUCP (Jonathan Hue)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: Help-Bus Errors
Keywords: what causes them
Message-ID: <7003@netcom.UUCP>
Date: 11 Feb 90 05:48:44 GMT
References: <1810@lzga.ATT.COM> <1990Feb10.192028.16025@eddie.mit.edu>
Organization: NetCom- The Bay Area's Public Access Unix System {408 249-0290 guest}
Lines: 12

In article <1990Feb10.192028.16025@eddie.mit.edu> aryeh@eddie.MIT.EDU (Aryeh M. Weiss) writes:
>Unix systems, dereferencing the dreaded NULL pointer.  SIGBUS errors are
>quite machine dependent, but in my experience can be caused by two
>circumstances

Another thing that can cause bus errors is accessing an address which
is a valid address within your process, but the thing at that location
doesn't respond to a read or write.  An example of this would be a
frame buffer that you mapped into your process' address space, but was
flaky and for some reason didn't generate DTACKs.

-Jonathan