Kevin OKeefe wrote:
I'd be about 95% sure that you have a problem.  Just because it works on the real device
> does not mean it's ok - probably you are lucking out and the corrupted memory (or
> whatever it is) just happens to not do something readily visible on the real device.
> I've come to trust POSER almost implicitly in these manners - if it is crashing,
there  is a problem with your code.

My 2 cents.
You raise a good point. And by no means have I ruled out the possibility that the code I'm writing is at fault.

But I'm left with a real conundrum. POSE is by all accounts the most useful tool available to me for debugging a problem like this. But whenever it hangs, I have to kill it, and down with it goes a lot of debugging data that might contain the answer I'm looking for. Does anyone have any suggestions for what I can do in a case like this? (Other than all of the Err[Non]FatalDisplayIf checks I'm already doing?)

--Larry


--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/

Reply via email to