If a debuggee is running and the user adds a breakpoint, the breakpoint does
not take effect until the next time the debuggee stops running. It should
have an immediate effect.
Implementation note: Need to silently stop the debuggee, set the breakpoint,
and resume running.
IMO this issue is not a defect. It is a request for enhancement.
A breakpoint cannot be set until the inferior program is stopped. But in some
cases the inferior program cannot be stopped (for example, waits for input),
so we need some way to show that this particular breakpoint is not set yet,
which means we need a new icon for such breakpoints.
There are several issues that block the implementation of this feature on Windows:
IZ 90120, IZ 89343.
Fixed (subject to the reliability of Pause on Windows).
It pretty much works as expected on Unix. But pretty much doesn't on Windows so I'll
leave the issue open and take a look at it on Windows next week.
Changing Platform/OS to PC/WindowsXP because this is fixed on Unix systems.
Blocked (on Windows) by 90120 and 89343.
Fixed with several caveats (see 90120 for details on the caveats). The main one
affecting this issue is that pausing Cygwin's gdb takes 20-30 seconds, so toggling
a breakpoint on a running process will take that 20-30 seconds before actually being
set. Its instantaneous with MinGW's gdb.
verified in build 200711020000