Author: jingham Date: Wed Mar 19 20:08:27 2014 New Revision: 204288 URL: http://llvm.org/viewvc/llvm-project?rev=204288&view=rev Log: More recent compilers emit debug info for the length property of NSString, so the length will be correctly reported as NSUInteger. Adopt the test case to handle either possibility.
Modified: lldb/trunk/test/lang/objc/foundation/TestRuntimeTypes.py Modified: lldb/trunk/test/lang/objc/foundation/TestRuntimeTypes.py URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/test/lang/objc/foundation/TestRuntimeTypes.py?rev=204288&r1=204287&r2=204288&view=diff ============================================================================== --- lldb/trunk/test/lang/objc/foundation/TestRuntimeTypes.py (original) +++ lldb/trunk/test/lang/objc/foundation/TestRuntimeTypes.py Wed Mar 19 20:08:27 2014 @@ -46,7 +46,7 @@ class RuntimeTypesTestCase(TestBase): # The length property should be usable. self.expect("expression str.length", VARIABLES_DISPLAYED_CORRECTLY, - substrs = ["(unsigned long long)"]) + patterns = [r"(\(unsigned long long\))|\(NSUInteger\)"]) # Static methods on NSString should work. self.expect("expr [NSString stringWithCString:\"foo\" encoding:1]", VALID_TYPE, _______________________________________________ lldb-commits mailing list lldb-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits