[Lldb-commits] [lldb] r178192 - This test case was not doing the right thing with libc++ being used and was generating spurious over-completion warning flags
Enrico Granata
egranata at apple.com
Wed Mar 27 16:08:54 PDT 2013
Author: enrico
Date: Wed Mar 27 18:08:54 2013
New Revision: 178192
URL: http://llvm.org/viewvc/llvm-project?rev=178192&view=rev
Log:
This test case was not doing the right thing with libc++ being used and was generating spurious over-completion warning flags
Modified:
lldb/trunk/test/functionalities/type_completion/TestTypeCompletion.py
Modified: lldb/trunk/test/functionalities/type_completion/TestTypeCompletion.py
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/test/functionalities/type_completion/TestTypeCompletion.py?rev=178192&r1=178191&r2=178192&view=diff
==============================================================================
--- lldb/trunk/test/functionalities/type_completion/TestTypeCompletion.py (original)
+++ lldb/trunk/test/functionalities/type_completion/TestTypeCompletion.py Wed Mar 27 18:08:54 2013
@@ -49,8 +49,10 @@ class TypeCompletionTestCase(TestBase):
# clean slate for the next test case.
def cleanup():
self.runCmd('type category enable gnu-libstdc++', check=False)
+ self.runCmd('type category enable libcxx', check=False)
self.runCmd('type category disable gnu-libstdc++', check=False)
+ self.runCmd('type category disable libcxx', check=False)
# Execute the cleanup function during test case tear down.
self.addTearDownHook(cleanup)
@@ -119,6 +121,7 @@ class TypeCompletionTestCase(TestBase):
self.assertFalse(string.IsTypeComplete(), 'std::string complete but it should not be')
self.runCmd('type category enable gnu-libstdc++', check=False)
+ self.runCmd('type category enable libcxx', check=False)
self.runCmd('frame variable guy --show-types')
p_vector = self.dbg.GetSelectedTarget().GetProcess().GetSelectedThread().GetSelectedFrame().FindVariable('p')
More information about the lldb-commits
mailing list