Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!wuarchive!decwrl!nsc!pyramid!leadsv!zech
From: zech@leadsv.UUCP (Bill Zech)
Newsgroups: comp.lang.c
Subject: Re: Bus Error
Summary: gets confusing, doesn't it?
Message-ID: <10406@leadsv.UUCP>
Date: 19 Mar 90 20:54:08 GMT
References: <16139.25F89344@urchin.fidonet.org> <690@ssp11.idca.tds.philips.nl>
Organization: LOCKHEED, Sunnyvale, CA
Lines: 23

In article <690@ssp11.idca.tds.philips.nl>, dolf@idca.tds.PHILIPS.nl (Dolf Grunbauer) writes:
> In article <1990Mar16.083052.20554@diku.dk> jensting@skinfaxe.diku.dk (Jens Tingleff) writes:
> }zech@leadsv.UUCP (Bill Zech) writes (at least I think he wrote it, ed. Dolf)
		    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
	
> }
> }>In the Motorola 68xxx series chips, a Bus Error is the result of some
> }
> }Or, of course, trying to fetch a long value from an address thats odd.. .
> }
> 

Actually, no, I didn't write that....

I wrote the long response that described the bus error from a 
hardware perspective.  

An just in case people are interested, a Spurious Interrupt is
a bus error during and interrupt acknowlege cycle.

No, I guess you weren't interested.  Oh well.

- Bill Zech