I should be able to at least get a stack crawl even if the debugger wasn't attached to begin with when the Simulator does display a fatal message. I think the problem in this case, though, is that I am using CW 9.3. It just occurred to me that if I attached the PalmDebugger at that point I could probably dump the stack. I'll try that as well.
-Aaron >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of >Benoit Cerrina >Sent: Tuesday, September 13, 2005 6:08 PM >To: Palm Developer Forum >Subject: Re: How to find a bug that crashes Simulator? > > >Of course you need to start your app with the debugger attached! Benoit > >Aaron Hansen wrote: > >>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 >> >> >> > > > > > > >_______________________________________________________________ >____________ >Appel audio GRATUIT partout dans le monde avec le nouveau >Yahoo! Messenger >Téléchargez cette version sur http://fr.messenger.yahoo.com > > >-- >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/
