[Lldb-commits] [lldb] r287893 - Fix TestMiExec.test_lldbmi_exec_next_instruction

[Pavel Labath via lldb-commits]

Author: labath
Date: Thu Nov 24 09:54:15 2016
New Revision: 287893

URL: http://llvm.org/viewvc/llvm-project?rev=287893&view=rev
Log:
Fix TestMiExec.test_lldbmi_exec_next_instruction

The line numbers come out slightly differently when the test is run with gcc-4.9
as a compiler. The test probably should not depend on that, but that is a
different story.

Modified:
    lldb/trunk/packages/Python/lldbsuite/test/tools/lldb-mi/control/TestMiExec.py

Modified: lldb/trunk/packages/Python/lldbsuite/test/tools/lldb-mi/control/TestMiExec.py
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/packages/Python/lldbsuite/test/tools/lldb-mi/control/TestMiExec.py?rev=287893&r1=287892&r2=287893&view=diff
==============================================================================
--- lldb/trunk/packages/Python/lldbsuite/test/tools/lldb-mi/control/TestMiExec.py (original)
+++ lldb/trunk/packages/Python/lldbsuite/test/tools/lldb-mi/control/TestMiExec.py Thu Nov 24 09:54:15 2016
@@ -252,7 +252,7 @@ class MiExecTestCase(lldbmi_testcase.MiT
         self.expect("\^running")
         # Depending on compiler, it can stop at different line
         self.expect(
-            "\*stopped,reason=\"end-stepping-range\".+?main\.cpp\",line=\"(29|30)\"")
+            "\*stopped,reason=\"end-stepping-range\".+?main\.cpp\",line=\"(28|29|30)\"")
 
         # Test that both --thread and --frame are optional
         self.runCmd("-exec-next-instruction")