Don’t use the resolved value to calculate the location unless the variable is in a register

This was causing a bunch of test cases to fail in python_api/process since they relied on SBValue::GetLocation()

llvm-svn: 181075

1 files changed, 5 insertions, 2 deletions

diff --git a/lldb/source/Core/ValueObjectVariable.cpp b/lldb/source/Core/ValueObjectVariable.cpp
index 8204f11e4b9..daff740399e 100644
--- a/lldb/source/Core/ValueObjectVariable.cpp
+++ b/lldb/source/Core/ValueObjectVariable.cpp
@@ -326,8 +326,11 @@ ValueObjectVariable::GetDeclaration (Declaration &decl)
 const char *
 ValueObjectVariable::GetLocationAsCString ()
 {
-    return GetLocationAsCStringImpl(m_resolved_value,
-                                    m_data);
+    if (m_resolved_value.GetContextType() == Value::eContextTypeRegisterInfo)
+        return GetLocationAsCStringImpl(m_resolved_value,
+                                        m_data);
+    else
+        return ValueObject::GetLocationAsCString();
 }
 
 bool