From e7687adc60e07af6850af7ad07786b58b40e19e2 Mon Sep 17 00:00:00 2001 From: Enrico Granata Date: Fri, 3 Oct 2014 01:48:32 +0000 Subject: Issuing a "type category disable *" command followed by a "type category enable *" command does not honor the order in which categories were previously enabled While we didn't really promise it would, it seems like it should This checkin enables just that, and fixes rdar://18527468 llvm-svn: 218949 --- lldb/source/DataFormatters/DataVisualization.cpp | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'lldb/source/DataFormatters/DataVisualization.cpp') diff --git a/lldb/source/DataFormatters/DataVisualization.cpp b/lldb/source/DataFormatters/DataVisualization.cpp index 8799c59..7ef0be5 100644 --- a/lldb/source/DataFormatters/DataVisualization.cpp +++ b/lldb/source/DataFormatters/DataVisualization.cpp @@ -196,6 +196,18 @@ DataVisualization::Categories::Disable (const lldb::TypeCategoryImplSP& category } void +DataVisualization::Categories::EnableStar () +{ + GetFormatManager().EnableAllCategories (); +} + +void +DataVisualization::Categories::DisableStar () +{ + GetFormatManager().DisableAllCategories(); +} + +void DataVisualization::Categories::LoopThrough (FormatManager::CategoryCallback callback, void* callback_baton) { GetFormatManager().LoopThroughCategories(callback, callback_baton); -- cgit v1.1