Mark test as expected-to-fail with GCC because some versions emit DWARF that claims

functions start at the line with the "{" character, whereas clang uses the first line
with source code. As such, this test case will only work with clang.

llvm-svn: 175808

1 files changed, 6 insertions, 0 deletions

diff --git a/lldb/test/functionalities/inline-stepping/TestInlineStepping.py b/lldb/test/functionalities/inline-stepping/TestInlineStepping.py
index 379fc3a4cea..3b7a0cb5ed5 100644
--- a/lldb/test/functionalities/inline-stepping/TestInlineStepping.py
+++ b/lldb/test/functionalities/inline-stepping/TestInlineStepping.py
@@ -18,6 +18,9 @@ class TestInlineStepping(TestBase):
         self.buildDsym()
         self.inline_stepping()
 
+    @expectedFailureGcc # Some versions of GCC emit DWARF that considers functions to start at the line with the '{' whereas this test
+                        # expects the first line of a function to be the first line of source (i.e. what clang does). As such, this test
+                        # fails with some versions of GCC.
     @python_api_test
     @dwarf_test
     def test_with_dwarf_and_python_api(self):
@@ -33,6 +36,9 @@ class TestInlineStepping(TestBase):
         self.buildDsym()
         self.inline_stepping_step_over()
 
+    @expectedFailureGcc # Some versions of GCC emit DWARF that considers functions to start at the line with the '{' whereas this test
+                        # expects the first line of a function to be the first line of source (i.e. what clang does). As such, this test
+                        # fails with some versions of GCC.
     @python_api_test
     @dwarf_test
     def test_step_over_with_dwarf_and_python_api(self):