[Lldb-commits] [lldb] r176357 - Update TestCallStdStringFunction to expected fail for gcc and account for multiple breakpoint locations.

[Matt Kopec]

Author: mkopec
Date: Fri Mar  1 11:29:16 2013
New Revision: 176357

URL: http://llvm.org/viewvc/llvm-project?rev=176357&view=rev
Log:
Update TestCallStdStringFunction to expected fail for gcc and account for multiple breakpoint locations.

Patch from Ashok Thirumurthi.


Modified:
    lldb/trunk/test/expression_command/call-function/TestCallStdStringFunction.py

Modified: lldb/trunk/test/expression_command/call-function/TestCallStdStringFunction.py
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/test/expression_command/call-function/TestCallStdStringFunction.py?rev=176357&r1=176356&r2=176357&view=diff
==============================================================================
--- lldb/trunk/test/expression_command/call-function/TestCallStdStringFunction.py (original)
+++ lldb/trunk/test/expression_command/call-function/TestCallStdStringFunction.py Fri Mar  1 11:29:16 2013
@@ -25,8 +25,8 @@ class ExprCommandCallFunctionTestCase(Te
         self.buildDsym()
         self.call_function()
 
-    @skipOnLinux #PR-15256: assertion failure in RecordLayoutBuilder::updateExternalFieldOffset
     @dwarf_test
+    @expectedFailureGcc # bugzilla 14437, fails with GCC 4.6.3 and 4.7.2
     def test_with_dwarf(self):
         """Test calling std::String member function."""
         self.buildDwarf()
@@ -36,7 +36,8 @@ class ExprCommandCallFunctionTestCase(Te
         """Test calling std::String member function."""
         self.runCmd("file a.out", CURRENT_EXECUTABLE_SET)
 
-        lldbutil.run_break_set_by_file_and_line (self, "main.cpp", self.line, loc_exact=True)
+        # Some versions of GCC encode two locations for the 'return' statement in main.cpp
+        lldbutil.run_break_set_by_file_and_line (self, "main.cpp", self.line, num_expected_locations=-1, loc_exact=True)
 
         self.runCmd("run", RUN_SUCCEEDED)