Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!msuinfo!frith!griffin
From: griffin@frith.uucp (Danny Griffin)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Unknown GURU numbers
Message-ID: <1991Mar11.065123.19384@msuinfo.cl.msu.edu>
Date: 11 Mar 91 06:51:23 GMT
References: <1991Mar10.072019.15764@zorch.SF-Bay.ORG>
Sender: news@msuinfo.cl.msu.edu
Organization: Michigan State University
Lines: 21

mike@zorch.SF-Bay.ORG (Mike Smithwick) writes:


>Is there a more complete source of GURU numbers than alerts.h? I'm always
>getting ones  which aren't listed. Just what the heck is 0x00000003 and
>0x0000000B?

0x03 is a CPU trap address error, and 0x0B is also a CPU trap, opcode 1111
(I believe that is a FPU or 680[23]0 instruction).  Both can be caused by
wild pointers, etc.  I used to see a lot of those when I first started
programming this beastie. :-)

I use GOMF and the errors are in that book, but there is also at least
one file of GURU numbers floating around on the BBSes and possibly the
Fish disks.
.


--
Dan Griffin
griffin@frith.egr.msu.edu