Remove @expectedFailureGcc from TestInlineStepping as function prologue bug is not reproducible anymore.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@185579 91177308-0d34-0410-b5e6-96231b3b80d8
diff --git a/test/functionalities/inline-stepping/TestInlineStepping.py b/test/functionalities/inline-stepping/TestInlineStepping.py
index 3b7a0cb..379fc3a 100644
--- a/test/functionalities/inline-stepping/TestInlineStepping.py
+++ b/test/functionalities/inline-stepping/TestInlineStepping.py
@@ -18,9 +18,6 @@
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):
@@ -36,9 +33,6 @@
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):