From: "Ben Combee" <[EMAIL PROTECTED]> > The simulator is a whole build of the OS with a Windows-based "device > abstraction layer". It's used for OS development at PalmSource, so usually > a crash in the sim is detected in the debugger of Visual Studio by a > developer that has full simulator source code. No source is available, > because the sim source is actually the whole OS source. > Excuse me? "It's used for OS development at PalmSource". My mistake then, because I thought it had been released as a tool for Palm OS developers. It's one thing to replace the robust, well built and useful emulator with a simple simulator - cheap, but that's life. It's something else to respond to complaints by suggesting that it's only an internal tool.
If it's an internal tool then Palm Source need to identify it as such and, on that basis, admit that OS 5 has no debugging environment. If it's not an internal tool but is intended for use as a debugging aid for third-party developers then let's have a debug build that doesn't crash when an ASSERT fails (I'm assuming that the crash is an ASSERT and not a simple failure to check API parameters). Which puzzles me because, as I'm typing this, I'm remembering that there *is* a debug version of the simulator and debug ROMS which, if I remember correctly, crashes just as badly as the 'release' stuff. What's the difference between the debug and release versions? I've also just noticed an early release of an ARM emulator for Palm OS 5.4 and 6. Is that intended to replace the simulator as the primary debugging tool or is it just for low level tech stuff? Chris Tutty -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
