forked from qt-creator/qt-creator
Debugger: Disable break on warning/fatal for cdb
This seems to cause more trouble than benefit. Additionally this option is on the _gdb_ extended settings site. Task-number: QTCREATORBUG-17902 Change-Id: Ie548f68f84bffee670559b48f6a2ba259f8b8757 Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
@@ -727,14 +727,14 @@ void CdbEngine::runEngine()
|
|||||||
runCommand({breakAtFunctionCommand(wideFunc, module), BuiltinCommand, cb});
|
runCommand({breakAtFunctionCommand(wideFunc, module), BuiltinCommand, cb});
|
||||||
runCommand({breakAtFunctionCommand(QLatin1String(CdbOptionsPage::crtDbgReport), debugModule), BuiltinCommand, cb});
|
runCommand({breakAtFunctionCommand(QLatin1String(CdbOptionsPage::crtDbgReport), debugModule), BuiltinCommand, cb});
|
||||||
}
|
}
|
||||||
if (boolSetting(BreakOnWarning)) {
|
// if (boolSetting(BreakOnWarning)) {
|
||||||
runCommand({"bm /( QtCored4!qWarning", BuiltinCommand}); // 'bm': All overloads.
|
// runCommand({"bm /( QtCored4!qWarning", BuiltinCommand}); // 'bm': All overloads.
|
||||||
runCommand({"bm /( Qt5Cored!QMessageLogger::warning", BuiltinCommand});
|
// runCommand({"bm /( Qt5Cored!QMessageLogger::warning", BuiltinCommand});
|
||||||
}
|
// }
|
||||||
if (boolSetting(BreakOnFatal)) {
|
// if (boolSetting(BreakOnFatal)) {
|
||||||
runCommand({"bm /( QtCored4!qFatal", BuiltinCommand}); // 'bm': All overloads.
|
// runCommand({"bm /( QtCored4!qFatal", BuiltinCommand}); // 'bm': All overloads.
|
||||||
runCommand({"bm /( Qt5Cored!QMessageLogger::fatal", BuiltinCommand});
|
// runCommand({"bm /( Qt5Cored!QMessageLogger::fatal", BuiltinCommand});
|
||||||
}
|
// }
|
||||||
if (runParameters().startMode == AttachCore) {
|
if (runParameters().startMode == AttachCore) {
|
||||||
QTC_ASSERT(!m_coreStopReason.isNull(), return; );
|
QTC_ASSERT(!m_coreStopReason.isNull(), return; );
|
||||||
notifyEngineRunOkAndInferiorUnrunnable();
|
notifyEngineRunOkAndInferiorUnrunnable();
|
||||||
|
|||||||
Reference in New Issue
Block a user