From 49bfafb5108a463f3c46c11d91d92c5528770928 Mon Sep 17 00:00:00 2001 From: Enrico Granata Date: Tue, 18 Nov 2014 23:36:25 +0000 Subject: Shuffle APIs around a little bit, so that if you pass custom summary options, we don't end up caching the summary hence obtained. You may want to obtain an uncapped summary, but this should not be reflected in the summary we cache. The drawback is that we don't cache as aggressively as we could, but at least you get to have different summaries with different options without having to reset formatters or the SBValue at each step llvm-svn: 222280 --- lldb/scripts/Python/interface/SBValue.i | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'lldb/scripts/Python') diff --git a/lldb/scripts/Python/interface/SBValue.i b/lldb/scripts/Python/interface/SBValue.i index db780394e71..728dae93249 100644 --- a/lldb/scripts/Python/interface/SBValue.i +++ b/lldb/scripts/Python/interface/SBValue.i @@ -122,7 +122,8 @@ public: GetSummary (); const char * - GetSummary (lldb::SBTypeSummaryOptions& options); + GetSummary (lldb::SBStream& stream, + lldb::SBTypeSummaryOptions& options); const char * GetObjectDescription (); -- cgit v1.2.3