*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, 2 insertions, 1 deletions

diff --git a/lldb/source/Commands/CommandObjectExpression.cpp b/lldb/source/Commands/CommandObjectExpression.cpp
index 86c2fd7d9a9..ca5ca1520f1 100644
--- a/lldb/source/Commands/CommandObjectExpression.cpp
+++ b/lldb/source/Commands/CommandObjectExpression.cpp
@@ -340,7 +340,8 @@ CommandObjectExpression::EvaluateExpression
                                               true,                     // Use synthetic children if available
                                               true,                     // Scope is already checked. Const results are always in scope.
                                               false,                    // Don't flatten output
-                                              0);                       // Always use summaries (you might want an option --no-summary like there is for frame variable)
+                                              0,                        // Always use summaries (you might want an option --no-summary like there is for frame variable)
+                                              false);                   // Do not show more children than settings allow
                 if (result)
                     result->SetStatus (eReturnStatusSuccessFinishResult);
             }