This only started happening to me when I "upgraded" CW5 to CW5.1
The debugger steps a lot slower now, even when I switch optimizations off.
Sometimes if you get stuck on a breakpoint, try turning it off then doing
'Step Into' -- 45% of the time it will step over it.
Some upgrade.
-Jeff Ishaq
The Windward Group
-----Original Message-----
From: Niel Skousen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 09, 1999 3:14 PM
To: [EMAIL PROTECTED]
Subject: Re: CW5 Debugger Stalls on Breakpoints
Mine (R5 patch2) has been doing this all along - BUT the greyed buttons
still work (SingleStep, StepIn, StepOver)
Good luck
Niel
At 03:00 PM 11/9/99 -0500, you wrote:
>Is anyone else seeing this behavior?
>
>I'm working on an application in CW5 (patched twice) and am using the new
>3.0a2 POSE. I'm writing in C++ and am using templates. More often than
>not, setting a breakpoint causes the emulator and debugger to just stop at
>the breakpoint except that the stack trace, variable and code widows stay
>empty. The emulator controls are disabled except for the "X" button which
>does in fact cancel the debugging session and reset the emulator.
>
>Needless to say, breakpoints have become fairly useless. Any ideas?
>
>-Paul
