Fixed a bug where a variable could not be formatted in a summary if its datatype already had a custom format

Fixed a bug where Objective-C variables coming out of the expression parser could crash the Python synthetic providers:
 - expression parser output has a "frozen data" component, which is a byte-exact copy of the value (in host memory),
   if trying to read into memory based on the host address, LLDB would crash. we are now passing the correct (target)
   pointer to the Python code
Objective-C "id" variables are now formatted according to their dynamic type, if the -d option to frame variable is used:
 - Code based on the Objective-C 2.0 runtime is used to obtain this information without running code on the target

llvm-svn: 136695

1 files changed, 3 insertions, 0 deletions

diff --git a/lldb/source/Commands/CommandObjectExpression.cpp b/lldb/source/Commands/CommandObjectExpression.cpp
index 6109b643fdc..86c2fd7d9a9 100644
--- a/lldb/source/Commands/CommandObjectExpression.cpp
+++ b/lldb/source/Commands/CommandObjectExpression.cpp
@@ -321,6 +321,9 @@ CommandObjectExpression::EvaluateExpression
         {
             if (result_valobj_sp->GetError().Success())
             {
+                
+                result_valobj_sp.get()->SetIsExpressionResult(true);
+                
                 if (m_options.format != eFormatDefault)
                     result_valobj_sp->SetFormat (m_options.format);