Aaron Hansen a écrit : > I still have > a hard time swallowing the idea that it is acceptable to be reduced to > the equivalent of printf's (logging) to find a crash in my code. > Breaking out on a memory exception is a basic feature I would expect of > any debugging environment.
It's half-consoling to see I'm not alone both experiencing Simulator crashes (on my own code errors, no doubt) and thinking the Simulator should do a better job at spotting those errors than plainly crashing. But until PalmSource addresses this issue, I'm afraid POSE will remain my debugging tool of choice, saving the Simulator for device-specific feature testing like hi-res or the T3 landscape mode. Or would on-device debugging with CW 9.3 yield better results? -- Luc Le Blanc -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
