feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

debugger: Make "set breakpoint of qFatal" optional

Browse Source 
This is mainly a workaround for cases where gdb crashes when setting
this breakpoint. It's unclear so far why this happens, but when it
happens, the debugger is basically useless, so there should be a
way to disable the "bad" feature.

Change-Id: I28ede9b38eb8bf56a8c5998088be487b4ee5896d
Reviewed-by: con
Task-number: QTCREATORBUG-5275
Reviewed-on: http://codereview.qt.nokia.com/1604
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
This commit is contained in:
hjk
2011-07-13 16:52:28 +02:00
committed by Eike Ziller
parent 1a63d5e625
commit 98a4f9ae71
5 changed files with 23 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/plugins/debugger/gdb/gdbengine.cpp
View File

@@ -4913,10 +4913,13 @@ void GdbEngine::handleNamespaceExtraction(const GdbResponse &response)
if (startParameters().startMode == AttachCore) {
notifyInferiorSetupOk(); // No breakpoints in core files.
} else {
postCommand("-break-insert -f '" + qtNamespace() + "qFatal'",
CB(handleBreakOnQFatal));
if (debuggerCore()->boolSetting(BreakOnWarning))
postCommand("-break-insert -f '" + qtNamespace() + "qWarning'");
if (debuggerCore()->boolSetting(BreakOnFatal))
postCommand("-break-insert -f '" + qtNamespace() + "qFatal'",
CB(handleBreakOnQFatal));
else
notifyInferiorSetupOk();
}
}