From 2aaab295746147ceb8a78a037c4e5e2ff8f1930e Mon Sep 17 00:00:00 2001 From: Pavel Labath Date: Wed, 15 Mar 2017 13:32:17 +0000 Subject: Fix TestMoveNearest for remote targets Launching a process with shared libraries on remote targets requires a special dance, which I forgot to do in r297830. llvm-svn: 297834 --- .../test/functionalities/breakpoint/move_nearest/TestMoveNearest.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (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 9d59a6fa298..26041c313e5 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 @@ -28,7 +28,8 @@ class TestMoveNearest(TestBase): 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()) + environment = self.registerSharedLibrariesWithTarget(target, ["foo"]) + process = target.LaunchSimple(None, environment, self.get_process_working_directory()) self.assertEquals(process.GetState(), lldb.eStateStopped) # Regardless of the -m value the breakpoint should have exactly one -- cgit v1.2.3