> I suggest you use PalmDebugger and forgo source level
> debugging.
By "PalmDebugger", are you referring to what is documented in the ..\Palm OS
Documentation\Palm OS Debugging on WIn.pdf? That is the document that shows
how to use the console commands.
Console commands are something I haven't resorted to up until now.
> Other than that, I'd just point out that you get a
> reset launch code when the device is reset, and the same goes for
> the emulator. You've got limited stack space (more so than usual)
> when launched in this way, and you're also limited in terms of
> which APIs you're allowed to use. I suggest avoiding anything
> even remotely tricky in this launch code
I'm not doing anything (that I know of) tricky or otherwise on a reset. Here
are the launch commands I specifically handle in PilotMain:
sysAppLaunchCmdNormalLaunch
sysAppLaunchCmdFind (the flag sysAppLaunchFlagNewGlobals is examined in my
code)
Mitch
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
