VaX#n8 (vax@ccwf.cc.utexas.edu) wrote:
: Steven's book defines SIGBUS as being generated due to an
: "implementation-defined" hardware fault.
: 
: Can someone please enumerate the faults which can cause a SIGBUS under
: NetBSD, particularly the i386 port?  Does access to a protected page give
: SIGBUS or SIGSEGV?

Should give SIGSEGV (though I didn't look at the code for -i386).

BUS is for thinks like:

on the m68k cpu's, code (or translation table?) accesses at odd
addresses, or accesses which are allowed by the MMU but lead to some
nonexistent hardware (the computer can detect), or to a parity error (if
implemented). 

Regards,
	Ignatios Souvatzis