Drivers don't access buses directly, but rather by reading from and writing to I/O or memory addresses, or by fielding interrupts. So I think any "bus error" message is going to be hardware-specific.
However a "buss error" would pertain to "software". ;-) -- Rod http://www.sunsetsystems.com/ On Monday 07 January 2002 16:18, Peter Jay Salzman wrote: > i did a google search, and found alot of conflicting answers. some of > them seemed to indicate that the precise definition of bus error is > architecture dependent, but i find that hard to believe. > > i know what a segmentation violation is. > > but what exactly is a bus error? > > can anyone write a hello world type program that demonstrates barfing > from a bus error? i found some code that purported to produce a bus > error on a sparc, but it didn't barf under linux. > > pete _______________________________________________ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
