diff options
| author | Pavel Labath <labath@google.com> | 2017-03-15 12:32:18 +0000 |
|---|---|---|
| committer | Pavel Labath <labath@google.com> | 2017-03-15 12:32:18 +0000 |
| commit | 32a8b7c3a7a0d5ed1133dc410fd9fc7306b63f7f (patch) | |
| tree | 32cd32fa34c49eda5e8cc1604afb1f373f64821c /lldb/packages/Python/lldbsuite/test | |
| parent | a156555b5e566a0682565243f87d6c9822b96ca3 (diff) | |
| download | bcm5719-llvm-32a8b7c3a7a0d5ed1133dc410fd9fc7306b63f7f.tar.gz bcm5719-llvm-32a8b7c3a7a0d5ed1133dc410fd9fc7306b63f7f.zip | |
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
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
| -rw-r--r-- | lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/move_nearest/TestMoveNearest.py | 4 |
1 files changed, 4 insertions, 0 deletions
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") |
