*Some more optimizations in usage of ConstString

*New setting target.max-children-count gives an upper-bound to the number of child objects that will be displayed at each depth-level
  This might be a breaking change in some scenarios. To override the new limit you can use the --show-all-children (-A) option
  to frame variable or increase the limit in your lldbinit file
*Command "type synthetic" has been split in two:
  - "type synthetic" now only handles Python synthetic children providers
  - the new command "type filter" handles filters
  Because filters and synthetic providers are both ways to replace the children of a ValueObject, only one can be effective at any given time.

llvm-svn: 137416

1 files changed, 3 insertions, 1 deletions

diff --git a/lldb/source/API/SBValue.cpp b/lldb/source/API/SBValue.cpp
index 1bfe211ec8f..58eb9794729 100644
--- a/lldb/source/API/SBValue.cpp
+++ b/lldb/source/API/SBValue.cpp
@@ -934,6 +934,7 @@ SBValue::GetDescription (SBStream &description)
         bool flat_output = false;
         bool use_synthetic = true;
         uint32_t no_summary_depth = 0;
+        bool ignore_cap = false;
         ValueObject::DumpValueObject (description.ref(), 
                                       m_opaque_sp.get(), 
                                       m_opaque_sp->GetName().GetCString(), 
@@ -946,7 +947,8 @@ SBValue::GetDescription (SBStream &description)
                                       use_synthetic,
                                       scope_already_checked, 
                                       flat_output,
-                                      no_summary_depth);
+                                      no_summary_depth,
+                                      ignore_cap);
     }
     else
         description.Printf ("No value");