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?

I have a research project which is giving a SIGBUS in malloc(), and I'm
trying to track down why.  (I have wrapped sbrk(), which is undoubtedly
related to the problem).  To be specific, line 195 of malloc.c.
-- 
VaX#n8 (vak-sa-nate) - n, CS senior++ and Unix junkie - vax@ccwf.cc.utexas.edu
Deal with evil through strength, yet encourage good through trust.    - PGP me