Often, an app that locks up the palm after a reset has a problem in its
PilotMain (usually accessing globals when it shouldn't). These types of
applications will often also have a problem after a sync, and when doing a
find from another application.
First, check to see whether your app locks up when doing a Find while
another application is open. If so, it's straightforward to set a breakpoint
in your PilotMain and then do the find.
If it doesn't lock up, then your PilotMain may be only failing while
handling the reset launch code. Change your PilotMain so it executes the
same code on a find as it does on a reset, and then try the find from
another app again. That'll cause the same environment (your app's PilotMain
executing while no global variables are available), and also the same code
(because you'll have your PilotMain executing your reset code during the
find).
Neil
> I have an app that locks up the palm whenever it resets (the palm dies while
> on the "welcome to OS3" opening splash screen. Does anyone know how I can
> debug this using CW debugger? I can step through the app OK , but how can I
> make the palm reset and still be in debug mode? There is a "reset" and
> "herd reset" options in the "debug" menu in CW, but they are always
> disabled, and they aren't in the help files either (at least not that I can
> find).
>
> thanks for any help!
>
> -Jeff Valore
> Triad Data Processing, Inc.
>
>
>
