I'm trying to get my game ready to ship... So I want to be a good developer and get it to pass a million Gremlins events. I'm not making it far at all (~20,000 events) before running into various problems.
I'm very motivated to find the reasons for my game screwing up in Gremlins, but I'm having some trouble with the tools. Do I just need to become better at using Palm Debugger? Is there a way to use CodeWarrior's source level debugger while using Gremlins? It would be great if I could investigate the call stack and variables from there. Or am I supposed to attach the Palm Debugger, run Gremlins, and then use the command line operations (e.g. "hd 2", etc) once Gremlins finds a problem? Sorry for the basic questions. I want to make sure I'm doing this stuff in the best way I can. Thanks! Eric http://www.sniderware.com -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
