Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!usc!merlin.usc.edu!girtab.usc.edu!aliu
From: aliu@girtab.usc.edu (Terminal Entry)
Newsgroups: comp.sys.amiga.tech
Subject: Re: PDC and debugging
Message-ID: <6473@merlin.usc.edu>
Date: 14 Nov 89 19:22:23 GMT
References: <SHEFFLER.89Nov14123841@maxwell.CS.CMU.EDU>
Sender: news@merlin.usc.edu
Reply-To: aliu@girtab.usc.edu (Terminal Entry)
Distribution: comp
Organization: University of Southern California, Los Angeles, CA
Lines: 16

In article <SHEFFLER.89Nov14123841@maxwell.CS.CMU.EDU> sheffler@maxwell.CS.CMU.EDU (Thomas Sheffler) writes:

>In UNIX I could look at the core dump to see where the program crapped
>out.  How can I see where an Amiga program is when it causes a GURU??

The GURU # should tell you. The address of the instruction that GURUed is
the last 6 numbers in the guru left to right. The first digits (before the
period) will tell you what kind of error. (i.e. CPU Trap, Exec error, etc).
There is a program called GURU I think that will decode the first 8 digits
of the GURU # for you. 

						aliu@nunki.usc.edu
						  Forwarded (MD)

(For example, 00000005.00299920f would mean CPU Trap, tried to divide
by 0, around hex 299920f...)