First off, let me say these are shots in the dark...but it sounds kinda
similar to 3 experiences I had under POSE.
The first one was happening because I was running a debug ROM. The
symptom is different, but the address beginning with 0x800* makes me
think of it. WinSetDrawWindow(NULL) was being called from within
EvtGetEvent(). On a real device, no problem. On a debug ROM, this made
my application quit with an error about accessing such a memory location
(even though my code clearly wasn't doing any such thing). In my case
that was fixed by explicitly setting the draw window immediately after
the EvtGetEvent, if running under POSE.
The second one was when I registered for a notification, but goofed at
the end of the application and didn't deregister for the notification.
The application quitting was causing the notification to happen, but the
code that was registered to respond to the notification had just gone
away...*boom* Simple to fix, once I realized what caused it.
The final one was I had written some assembly code, and trashed one of
the a* registers (a3, I think). Anyway, I slapped in a
movem.l %%d0-%%a3,-(%%sp)
at the beginning of the assembly function, and a
movem.l (sp)+,%%d0-%%a3
at the end protecting all the registers I was using, and the problem was
solved.
I only mention these in the hope that one helps scare the bug out into
the daylight...;^)
-Ken
On Sat, 2002-10-26 at 18:27, Richard Coutts wrote:
> I'm getting an error when I kill a debug run that I don't know where its
> coming. I start POSE and then hit F5 to start my debug session. Everything
> goes well. Then when I cancel the debug session by (either by closing the
> debug window or "Debug>Kill"), POSE resets (as usual) and then gives the
> error:
>
> MyApp (1.0) just changed the emulated program counter to
> 0x8003A6A6. This address is invalid because it's in neither ROM nor
> RAM.
>
> And the usu. button [Debug] [Reset...] buttons. But, when I hit [Debug] the
> error message goes away and then comes back (I guessing that it can't debug
> at this point, because the debug window has been killed).
>
> Its a tough error to debug because it does not rear its ugly head until the
> debug session is killed. I'm at a loss as to where to begin to look for the
> error and could really use some pointers as to what might be going on.
>
> Thanks!
> Rich
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe, please see
>http://www.palmos.com/dev/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
