commit 3880c4cebd5ce015dffb180d8905797f75a76362
author Enrico Granata <egranata@apple.com> Fri May 03 23:28:47 2013 +0000
committer Enrico Granata <egranata@apple.com> Fri May 03 23:28:47 2013 +0000
tree 5525dcb76a7497509562816587556c421bea13f8
parent b23b11300abd49c251d16bb491c004d597b5e19e

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

lldb/source/Core/ValueObjectVariable.cpp

diff --git a/lldb/source/Core/ValueObjectVariable.cpp b/lldb/source/Core/ValueObjectVariable.cpp
index 8204f11..daff740 100644
--- a/lldb/source/Core/ValueObjectVariable.cpp
+++ b/lldb/source/Core/ValueObjectVariable.cpp
@@ -326,8 +326,11 @@
 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