I have had something similar happen to me. I start debugging, then hit a breakpoint. It has happened to me when I hit F5 (or the Run icon) or when I single-step (sometimes after several single-steps) (could be either the step inside or step over).

It's not a show-stopper for me - I can usually stop the debugging session and then start up again. The only thing is that it is usually repeatable (if it happens once, it happens again). It doesn't go away if I remove and then re-set the breakpoint. I should also point out that I do not turn on code optimization.

This has only happened when I have been debugging with POSE. I've never had it happen when I'm debugging on the device or with any of the various Palm OS Simulator flavors.

At 03:00 AM 1/6/2004, Ben Combee <[EMAIL PROTECTED]> wrote:
At 10:41 PM 1/5/2004, Luc Le Blanc wrote:
>I run CW 8.3. Regularly, I quit a debug session with set breakpoints. If I
>start another debug session with the same PRC, previous breakpoints
>remain, but
>I cannot go beyond the first one I hit, the blue arrow sticks onto it and
>control hangs. Deleting all breakpoints usually doesn't do any good: running a
>new debug session still stops and hangs at the previous breakpoints. Was this
>solved in CW 9.2?


I don't remember this bug being reported in 8.3, and I've not seen similar
behavior in any of the 9.x builds.

When you say "quit a debug session", are you working with POSE, PalmSim, or
a device?  There are potential problems with ending a session with POSE and
having it set to "save your state", as that could save PRCs with embedded
breakpoints.  This is one of the big reasons that V9 has POSE start/stop
support, where POSE is killed at the end of the debug session, making sure
that when it starts back up, the session will be clean.

----
Tom Frauenhofer, [EMAIL PROTECTED]
http://www.beret.com




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

Reply via email to