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>
This commit is contained in:
hjk
2014-11-27 14:43:45 +01:00
parent 804497c32c
commit f2e7ec6e3f

View File

@@ -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).