forked from qt-creator/qt-creator
Debugger: Pass uninitialized variables to the python dumpers
Reduces accessing uninitialized memory Change-Id: I025e9070b9b17a806237619b484cb27230e7f494 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
This commit is contained in:
@@ -1238,6 +1238,13 @@ void CdbEngine::doUpdateLocals(const UpdateParameters &updateParameters)
|
||||
cmd.arg("stringcutoff", action(MaximalStringLength)->value().toString());
|
||||
cmd.arg("displaystringlimit", action(DisplayStringLimit)->value().toString());
|
||||
|
||||
if (boolSetting(UseCodeModel)) {
|
||||
QStringList uninitializedVariables;
|
||||
getUninitializedVariables(Internal::cppCodeModelSnapshot(),
|
||||
frame.function, frame.file, frame.line, &uninitializedVariables);
|
||||
cmd.arg("uninitialized", uninitializedVariables);
|
||||
}
|
||||
|
||||
cmd.callback = [this](const DebuggerResponse &response) {
|
||||
if (response.resultClass == ResultDone) {
|
||||
showMessage(response.data.toString(), LogMisc);
|
||||
|
||||
Reference in New Issue
Block a user