aboutsummaryrefslogtreecommitdiffstats
path: root/src/plugins/debugger/breakhandler.cpp
diff options
context:
space:
mode:
authorhjk <[email protected]>2015-07-16 08:49:43 +0200
committerhjk <[email protected]>2015-07-16 11:52:32 +0000
commitc81407f28db0df84906984dd6a4e5d665df6070c (patch)
treec22164d0fa0310e439a0638da6fe58ecb83fc0ca /src/plugins/debugger/breakhandler.cpp
parent0bc18df6554acdcc91654e719c0ee49482d21d2d (diff)
Debugger: Lift restriction one-shot breakpoints deletion
This was/is a workaround to not lose the extra information carefully crafted one-shot-breakpoints might carry (e.g. conditions). However, it gets into the way when simple one-shot breakpoints are used automatically ("Jump to line", or native-mixed debugging), so actually deleting the bp in the ui if it's gone on the debugger side seems the lesser evil nowadays. Change-Id: If00dc4e8f27881236c05b17109b57d7c53d424ab Reviewed-by: Christian Stenger <[email protected]>
Diffstat (limited to 'src/plugins/debugger/breakhandler.cpp')
-rw-r--r--src/plugins/debugger/breakhandler.cpp1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/plugins/debugger/breakhandler.cpp b/src/plugins/debugger/breakhandler.cpp
index 969b011a9c5..baaef60d340 100644
--- a/src/plugins/debugger/breakhandler.cpp
+++ b/src/plugins/debugger/breakhandler.cpp
@@ -802,6 +802,7 @@ bool Breakpoint::isOneShot() const { return parameters().oneShot; }
void Breakpoint::removeAlienBreakpoint()
{
+ b->m_state = BreakpointRemoveProceeding;
b->deleteThis();
}