"Steve Achelis" <[EMAIL PROTECTED]> wrote in message
news:36936@palm-dev-forum...
>
> There was a very long thread on this subject in December. It was solved
by
> the developer switching to POSE 3.0a8. Unfortunately, I'm having the same
> problem and it happens with 3.0a8 (and 3.0a7).
>
> If I put a breakpoint (using CW7) in PilotMain() (and in MyMain() where I
> handle sysAppLaunchCmdSystemReset), they don't get triggered following
Reset
> in POSE. Shouldn't they?
>
> Also, sometimes the message is stack overflow, but usually the debugger
pops
> up in the weeds (i.e., in my code, but code that shouldn't be executing).
> The last three items on the call stack are my functions (which I don't
think
> were called, at least break points in them were never triggered and they
> aren't related to startup). Then the call stack shows (in reverse order)
> the system calls: PrivCallSafely, SysAppLaunch, SysBroadcastActionCode,
etc.
> It seems as if the Reset command is calling into the middle of my code,
> rather than into my PilotMain().
No... the problem is that CW doesn't detect the reset so it isn't able to
maintain some state about the program database needed to debug correctly.
Symptoms can include not stopping and stopping in the program but showing
the wrong source.
If you want to test your post reset behavior, change the launch code the CW
debugger sends from the PalmOS debug panel.
--
Ben Combee
Veriprise Wireless <http://www.veriprise.com>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
