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 is my pilot main...untouched since I started writing this program 2
years ago.
{
Err error;
error = RomVersionCompatible (version20, launchFlags);
if (error) return (error);
switch (cmd)
{
case sysAppLaunchCmdNormalLaunch:
error = AppStart();
if (error)
return error;
FrmGotoForm(MainForm);
AppEventLoop();
AppStop();
break;
default:
break;
}
return 0;
}
I dont even do anything during that event so why is it complaining? What am
I missing? It's really annoying because everytime I stop debugging, the Emu
wont even reset...I have to "Turn Extensions off" in order for it to come up
again or the error will just continue to occur. BTW, I searched at escribe
(wow, a lot better than searching at yahoo!) for "global variable", "launch
code", and "sysAppLaunchcmdSystemReset" and didnt find anything like this.
Another problem: if I turn on "memory Leak Detection" I get a memory leak
that I cant track down...Other ones were obvious but this one looks like
it's from within the system?
>From the Emu log.
Relocatable chunk leaked at 0x00001D74, size = 272
555.375: Chunk allocated by:
555.375: ResLoadForm
555.375: FrmInitForm
555.375: AppHandleEvent__FP9EventType
555.375: AppEventLoop__Fv
555.375: StarterPilotMain__FUsPvUs
555.375: PilotMain
555.375: <Unknown @ 0x000272CC>
If I debug it, it puts me in the middle of some system code.
Any thoughts?
TIA,
Mike
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
