If only it were so! I am using the debug version of the simulator. It does catch some more simple API errors such as drawing to a bad window, but I can't even get a stack track for these if the debugger is not already attached. Furthermore the debug simulator still GPF's if I generate a memory exception in my code. Mistakes handling memory and pointers are just so common I don't see how Palm can justify this stance that it's ok to let the Simulators GPF like that.
I haven't tried attaching VS to the Simulator. That would be worlds better if I could at least do that to get a stack. I'll give it a try just to make sure. I had assumed the symbols wouldn't be there as you said might be the case. Thanks, Aaron >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Ben Combee >Sent: Tuesday, September 13, 2005 4:50 PM >To: Palm Developer Forum >Subject: RE: How to find a bug that crashes Simulator? > > >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. > >You might also be able to tell somethings by using a Win32 >debugger, like >Visual Studio, to run the simulator. When a crash happens, >you may be able >to see the stack crawl, although I think those symbols might >not be turned on. > > >-- 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/ > > -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
