"Robert McKenzie" <[EMAIL PROTECTED]> wrote in message news:75012@palm-dev-forum... > > To debug an app that fatal errors on install, you must identify the code > that is executing on install and make it run -- in the same state -- under > the debugger when the debugger loads the application. > > Normally this is code that runs in response to sync notification launch > code. My standard trick with this is to create a custom build of the app > that does not respond to either the sync notification launch code or the > normal launch code, but that does execute the deadly code in response to the > find launch code. Then you can use the debugger to load the application, do > a "go" in Pilot main, and then do a find. Set a breakpoint at the top of > the code you suspect & go to town.
With CodeWarrior V8, you can also just directly launch your program from the debugger with the appropriate launch code (as set in the Palm Debugger panel). However, the debugger always uses a SysUIAppSwitch, so you'll always have globals available. (Ben just thought of a new feature for V9's debugger :) -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
