From 081d56c4d9789ad4643c138fe8a058277fab60d1 Mon Sep 17 00:00:00 2001 From: Rene Gollent Date: Tue, 10 Nov 2015 12:24:03 -0500 Subject: [PATCH] Debugger: Fix potential VariablesView crash. - In some contexts, VariablesView doesn't have an associated thread and stack frame, which would lead to a potential crash when resolving expression nodes. --- .../debugger/user_interface/gui/team_window/VariablesView.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/apps/debugger/user_interface/gui/team_window/VariablesView.cpp b/src/apps/debugger/user_interface/gui/team_window/VariablesView.cpp index c81142d4d9..4e2fc13cff 100644 --- a/src/apps/debugger/user_interface/gui/team_window/VariablesView.cpp +++ b/src/apps/debugger/user_interface/gui/team_window/VariablesView.cpp @@ -2560,8 +2560,8 @@ VariablesView::_RequestNodeValue(ModelNode* node) containerLocker.Unlock(); // request resolution of the value - fListener->ValueNodeValueRequested(fStackFrame->GetCpuState(), container, - valueNode); + fListener->ValueNodeValueRequested(fStackFrame != NULL + ? fStackFrame->GetCpuState() : NULL, container, valueNode); }