From 32a8b7c3a7a0d5ed1133dc410fd9fc7306b63f7f Mon Sep 17 00:00:00 2001 From: Pavel Labath Date: Wed, 15 Mar 2017 12:32:18 +0000 Subject: Fix TestMoveNearest breakage on darwin It seems that on darwin we are not able to resolve breakpoints in the test shared library until the process has started. That seems unfortunate, but it is not the purpose of this test, so work around that by starting the process before doing the rest of our checks. llvm-svn: 297830 --- .../test/functionalities/breakpoint/move_nearest/TestMoveNearest.py | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'lldb/packages/Python/lldbsuite/test/functionalities') diff --git a/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/move_nearest/TestMoveNearest.py b/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/move_nearest/TestMoveNearest.py index ae58ad9960d..9d59a6fa298 100644 --- a/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/move_nearest/TestMoveNearest.py +++ b/lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/move_nearest/TestMoveNearest.py @@ -27,6 +27,10 @@ class TestMoveNearest(TestBase): target = self.dbg.CreateTarget("a.out") self.assertTrue(target, VALID_TARGET) + lldbutil.run_break_set_by_symbol(self, 'main', sym_exact=True) + process = target.LaunchSimple(None, None, self.get_process_working_directory()) + self.assertEquals(process.GetState(), lldb.eStateStopped) + # Regardless of the -m value the breakpoint should have exactly one # location on the foo functions self.runCmd("settings set target.move-to-nearest-code true") -- cgit v1.2.3