Re: [Lldb-commits] [lldb] r319472 - Fix this test so that the breakpoints you set are

2017-12-04 Thread Pavel Labath via lldb-commits
Gdb has no issues with this use case. I'm pretty sure this is a problem with how our posix dynamic linker plugin catches these events. I've asked eugene to look into that. On 1 December 2017 at 18:58, Jim Ingham wrote: > The fact that this passes on macOS likely does mean the general mechanism >

Re: [Lldb-commits] [lldb] r319472 - Fix this test so that the breakpoints you set are

2017-12-01 Thread Jim Ingham via lldb-commits
The fact that this passes on macOS likely does mean the general mechanism works but that the Linux library loading hook gets called too late, so you probably can't fix it in lldb. Be interesting to see if gdb has the same problem. Jim > On Dec 1, 2017, at 3:09 AM, Pavel Labath wrote: > > coo

Re: [Lldb-commits] [lldb] r319472 - Fix this test so that the breakpoints you set are

2017-12-01 Thread Pavel Labath via lldb-commits
cool. thanks. On 30 November 2017 at 20:43, Jim Ingham via lldb-commits wrote: > Author: jingham > Date: Thu Nov 30 12:43:00 2017 > New Revision: 319472 > > URL: http://llvm.org/viewvc/llvm-project?rev=319472&view=rev > Log: > Fix this test so that the breakpoints you set are > unambiguously on o

[Lldb-commits] [lldb] r319472 - Fix this test so that the breakpoints you set are

2017-11-30 Thread Jim Ingham via lldb-commits
Author: jingham Date: Thu Nov 30 12:43:00 2017 New Revision: 319472 URL: http://llvm.org/viewvc/llvm-project?rev=319472&view=rev Log: Fix this test so that the breakpoints you set are unambiguously on one bit of code. On macOS these lines mapped to two distinct locations, and that was artificiall