From: "Aaron Hansen" <[EMAIL PROTECTED]> > Is this not an issue for anyone else? I'd at least like to know if > other people are able to trap fatal errors in any simulator without it > GPF'ing too. It's not like the old days when I had the source code for > the POSE and I could just throw it in the debugger and track down the > crash myself. Or is it? Is the source for any of the simulators > available? > My experience has been that a crash in the simulator was usually caused by a bug in my code resulting in either memory corruption or an API call being passed an invalid value. The simulator, because it's just a copy of the normal Palm OS ROM, can't handle this and dumps out.
This, unfortunately, makes it a much less powerful debugging aid than the emulator (which could tell you about stuff like null pointers and memory corruption) but it's a lot cheaper to build this way for PalmSource. The bottom line is that you first need to gaurantee that your code isn't causing the crash and to do that you've got to employ the same sort of strategies as debugging on the device - log to the screen, log to a db, log to a VFS file, etc. The crash is far more likely to be a bug in your code than a bug in the Palm OS source and, if it is a bug in the Palm OS source you're down to debugging assembler because you're not going to get access to the Palm OS source. Chris Tutty -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
