It is partially true.
You can pause the debugger, put your breakpoint and resume it.
I think a one time 'add breakpoint' is what we need.
This has been one of the things that have driven me crazy ;-)
I don't know what you are all talking about... At least on Windows, adding/removing a breakpoint while already debugging works just fine. I do it every day...?! Might someone enlighten me? Is this a Linux issue?!
if (!IsStopped())
return false;
Using the GDB debugger plug-in, if the debugger is running (not just in "debug mode", mind you, but the debug target is currently running) my attempts to add a breakpoint are ignored.I am telling you: I *am* in debug mode and I *am* in the process of debugging an application (e.g. a BP has just hit). And while doing this I can just add/remove BP's on the fly. Just as I said. Shall I make a video or what?!
I am telling you: I *am* in debug mode and I *am* in the process of debugging an application (e.g. a BP has just hit). And while doing this I can just add/remove BP's on the fly. Just as I said. Shall I make a video or what?!
Note that you said "a BP has just hit". What the rest of us are talking about is if a breakpoint hadn't just hit. What if there were no breakpoints...the program was just running...and you wanted to add one?Ah - OK. Confirmed... Phew... that was a hard way to go. I was already under the assumption I am a complete idiot. ;-)
Put another way, when debugging you can only edit breakpoints while the debugger is paused.