From: "Ben Combee" <[EMAIL PROTECTED]> > Make sure you're using a debug version of the simulator. That has a lot > more checks, since the assertions are turned on in the OS code. When one > it hit, you should be able to hit the "debug in 68K" button and see your > stack crawl. > If someone identifies a crash as relating to a situation where an assert seems to be missing (perhaps a bad API parameter crashing the simulator rather than triggering an assertion) is there any value in raising this as a bug, or would it be ignored because it doesn't affect the real-world behaviour of Palm OS?
I realise that it's a gray area, but I'm thinking that this at least would allow us to gradually improve the robustness of the simulator as a debugging tool, although it depends on PalmSource being willing to apply resources to those bug reports. Chris Tutty -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
