At 03:10 PM 9/12/2002 -0700, you wrote: >Either I write incredibly bad code (wouldn't put it past me), or the >Emulator is just too sensitive. Seems like ever since I upgraded to the >latest version, even with all the debugging options off, I still get the Emu >complaining about one thing or another. > >Right now every time I stop the debugging in CW, the Emu gives me "Accessed >memory.... which means you are accessing global variables during a >SysAppLaunchCmdSystemReset." I didn't change anything, and it never >complained before.
Here's a way to find this problem: 1) Use the debugger panel to launch your application using the SysAppLaunchCmdSystemReset launch code. You will launch with globals when using V8, but this code will be passed to your app. 2) At the automatic breakpoint at the start of PilotMain, open the registers window and change the value of A5 to 0x01. This will cause any access relative to A5 (i.e. global access) to cause a bus error. 3) Step through your code until you're about to exist PilotMain. Hopefully, you'll easily be able to see the global access and fix it. You can also just try downloading you app as normal with the debugger, exiting to the launcher, then using a global find. That will sublaunch your app while its still locked in memory, and it should show the same symptoms. -- Ben Combee <[EMAIL PROTECTED]> CodeWarrior for Palm OS technical lead Palm OS programming help @ www.palmoswerks.com -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
