I'm having a very general problem on a big project runing on a real
IIIx. (It works perfectly on the debugger.) It's not the kind of
project that I can encapsulate (at least not yet), although I have
smaller projects that do work fine on the real IIIx.
On my project - in all different sections of my code - if I just run it
directly from the launcher or debug run it (F5) [on the real IIIx], it
goes through a few pages of code and then locks up - the IIIx freezes
and has to be manually reset.
But if I single step through the same code, or set break points not to
far from each other, all of the code works perfectly.
I can single step it all day, getting it to all different parts of my
code, but the moment I hit F5 the IIIx locks up - HARD.
My trace output shows nothing unusual other than the program stopped
executing soon after I hit F5. And again, if I just run it from the
launcher it still locks up, so it's more than the act of debugging that
makes it lock.
So I'm racking my brain trying to think of what types of problems might
be stabilized by single stepping in a debugger...
I know this is a long shot question, but I'm getting hammered hard this
time, so I thought I'd at least ask.
So for now, I'm just asking if anyone out there experienced this kind of
thing on their own project, and if they found a meaning behind it.
Thanks guys. :)
- Jeff
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
