Path: utzoo!news-server.csri.toronto.edu!rutgers!cbmvax!cbmehq!cbmfra!swinjm!forgeas
From: forgeas@swinjm.UUCP (Jean-Michel Forgeas)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Unknown GURU numbers
Message-ID: <18d1cfcc.ARN0b7a@swinjm.UUCP>
Date: 13 Mar 91 11:36:44 GMT
References: <1991Mar10.072019.15764@zorch.SF-Bay.ORG> <kenny.3232@mazurka.UUCP>
Reply-To: forgeas@swinjm.UUCP (Jean-Michel Forgeas)
Followup-To: comp.sys.amiga.programmer
Organization: The Software Winery
Lines: 34

In article <kenny.3232@mazurka.UUCP>, Kenneth Yarnall writes:

> In article <1991Mar10.072019.15764@zorch.SF-Bay.ORG> 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?
>
> _Mapping the Amiga_ by Anderson and Thompson (Compute Books, 1990, ISBN
> 0-87455-195-1) has a bunch on them in an appendix (well, all the ones I've
> ever gotten, anyway :).  It lists 00000003 as implying an Adderss error (a CPU
> exception, and 0000000B as Op code 1111.

Yes but not everybody knows that an address error is an odd address.
To search your bug without rebooting every time, you could do something
like that:

- an example of code where pointer could be odd:
    long *pointer = (long *) foo->UserData;
    *pointer = value;   <-- boom!

- test pointer with a small change:
    long *pointer = (long *) foo->UserData;
    if (pointer & 1) { printf("Hi Mike this is there!!!\n"); return; }
    *pointer = value;

Best regards,
--
                                     \___/
Jean-Michel Forgeas                   \-/
cbmvax!cbmehq!cbmfra!swinjm!forgeas    |    The Software Winery
                                      -^-
                           And, where is the universe ?