diff options
| author | hjk <hjk121@nokiamail.com> | 2014-11-27 14:43:45 +0100 |
|---|---|---|
| committer | hjk <hjk121@nokiamail.com> | 2014-11-27 15:14:10 +0100 |
| commit | f2e7ec6e3f25feca9e11ef060110da6451fe93b7 (patch) | |
| tree | e7181d2098b16b1b70619c82adb83eabb060bb8d | |
| parent | 804497c32cd1ad393661d0fa1f6ef63fb978ad0d (diff) | |
| download | qt-creator-f2e7ec6e3f25feca9e11ef060110da6451fe93b7.tar.gz | |
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 <christian.stenger@theqtcompany.com>
| -rw-r--r-- | src/plugins/debugger/gdb/gdbengine.cpp | 2 |
1 files changed, 2 insertions, 0 deletions
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). |