Re: [Lldb-commits] [lldb] r297830 - Fix TestMoveNearest breakage on darwin

2017-03-15 Thread Jim Ingham via lldb-commits
Finding the executables that a binary will load on run before you actually run is always best effort. We don't require the ObjectFile class to fully emulate the platform loader. So from the standpoint of writing tests, if the test relies on getting symbols from a loaded library it should alway

Re: [Lldb-commits] [lldb] r297830 - Fix TestMoveNearest breakage on darwin

2017-03-15 Thread Pavel Labath via lldb-commits
Hi Jim, I am not sure if behavior like this should be considered a bug, but I wanted to make sure you don't miss this. cheers, pl On 15 March 2017 at 12:32, Pavel Labath via lldb-commits wrote: > Author: labath > Date: Wed Mar 15 07:32:18 2017 > New Revision: 297830 > > URL: http://llvm.org/vi

[Lldb-commits] [lldb] r297830 - Fix TestMoveNearest breakage on darwin

2017-03-15 Thread Pavel Labath via lldb-commits
Author: labath Date: Wed Mar 15 07:32:18 2017 New Revision: 297830 URL: http://llvm.org/viewvc/llvm-project?rev=297830&view=rev Log: 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