That's right, I forgot about that. Now that you mention it I remember someone else asking about the Simulator source and hearing that explanation. Too bad you couldn't wrap the OS in a library and just release the supporting Simulator source. I'm sure today's legal landscape makes it more complicated than that (thanks lawyers). I know I for one would be more than happy to help track down Simulator bugs and turn them in. I've done it in the past with POSE anyhow.
It would be nice if there was something like the debugprefs app for the simulator that could at least trap the reset and let me capture a stack trace. Even if it was assembly it would be a little more helpful. Does the simulator function any better with the PalmDebugger? I use that with the debugprefs app on my Treo650 to trap resets and dump the stack. The nice thing is I don't have to have the device hooked up to the cable ahead of time. If anyone is trying to find an elusive reset I recommend this approach. Thanks for the response Ben, Aaron >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Ben Combee >Sent: Tuesday, September 13, 2005 11:17 AM >To: Palm Developer Forum >Subject: RE: How to find a bug that crashes Simulator? > > >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. > >-- Ben Combee, Senior Software Engineer, Palm, Inc. > "Combee on Palm OS" weblog: http://palmos.combee.net/ > Developer Forum Archives: http://news.palmos.com/read/all_forums/ > > -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
