At 04:49 PM 9/13/2005, you wrote:
I can buy the "cheaper" reasoning. That would make sense. I still have
a hard time swallowing the idea that it is acceptable to be reduced to
the equivalent of printf's (logging) to find a crash in my code.
Breaking out on a memory exception is a basic feature I would expect of
any debugging environment.
I never suggested I want to find bugs in the PalmOS code. I want to
find bugs in my code. Of course we try to garuntee that we never
generate a memory exception or use an API incorrectly, but that is going
to happen with a code base as large as the one I work with (60 segments
to give you an idea). There are several developers touching the same
code, and some of it is code that is common to other plaforms like
Symbian, PPC and SmartPhone. When it does happen the simulator should
not GPF. No amount of discussion will convince me that is "OK".
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/
