From f2e7ec6e3f25feca9e11ef060110da6451fe93b7 Mon Sep 17 00:00:00 2001 From: hjk Date: Thu, 27 Nov 2014 14:43:45 +0100 Subject: Debugger: Fix parsing of single-shot breakpoints from GDB response This can be manually triggered by entering e.g 'tbreak file.cpp:1' in the debugger input pane. Change-Id: I8212e82d258bb488fc1848e7d7e3e9ff5a3cae88 Reviewed-by: Christian Stenger --- src/plugins/debugger/gdb/gdbengine.cpp | 2 ++ 1 file changed, 2 insertions(+) (limited to 'src') diff --git a/src/plugins/debugger/gdb/gdbengine.cpp b/src/plugins/debugger/gdb/gdbengine.cpp index 8862f1ebc1..fcba0c320c 100644 --- a/src/plugins/debugger/gdb/gdbengine.cpp +++ b/src/plugins/debugger/gdb/gdbengine.cpp @@ -2382,6 +2382,8 @@ void GdbEngine::updateResponse(BreakpointResponse &response, const GdbMi &bkpt) response.condition = child.data(); } else if (child.hasName("enabled")) { response.enabled = (child.data() == "y"); + } else if (child.hasName("disp")) { + response.oneShot = child.data() == "del"; } else if (child.hasName("pending")) { // Any content here would be interesting only if we did accept // spontaneously appearing breakpoints (user using gdb commands). -- cgit v1.2.1