Debugger: may appear as if stopped at a (disabled) breakpoint

Prepare some break points - some of the break points should be hit almost on startup of the application.

Disable a couple of the early break points and start debugging.

The debugger stack trace appears and indicates to have stopped at one of the disabled break points, but in fact it still runs (the inferior can be used, the debugger toolbar indicates "interrupt" instead of "continue")