I can guarantee that it's not from a saved image (I have a specific set of
POSE image configurations that I've built up to test various device/data
configurations, I rarely save POSE images). When it happens it's usually
not the first time I've tried debugging my program in that POSE session
Ben Combee a écrit :
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
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
At 12:28 PM 1/6/2004, Tom Frauenhofer wrote:
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).
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:
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
