> On Feb 15, 2018, at 3:56 AM, Dmitry Antipov via lldb-dev
> wrote:
>
> On 02/15/2018 02:21 PM, Pavel Labath wrote:
>
>> I've tried your sample, and I was indeed able to reproduce the
>> problem. What makes your case special is that "sin" and "cos" are
>> indirect functions (STT_GNU_IFUNC), s
Yes, it looks that way, but I cannot reproduce this on my side (which
is not surprising as it involves parsing debug info from your dynamic
linker). I'd need the relevant portions of that file (or just the
whole file) to see what's going on there.
That said, this shouldn't impact you unless you pl
On 02/15/2018 02:21 PM, Pavel Labath wrote:
I've tried your sample, and I was indeed able to reproduce the
problem. What makes your case special is that "sin" and "cos" are
indirect functions (STT_GNU_IFUNC), so we have to do some extra work
(call the resolver function) to resolve them.
I've
+ eugene as the "most recent person who worked on the DYLD plugin" :D
Hi Dmitry,
I've tried your sample, and I was indeed able to reproduce the
problem. What makes your case special is that "sin" and "cos" are
indirect functions (STT_GNU_IFUNC), so we have to do some extra work
(call the resolver
I'm trying to setup a pending breakpoint for sin() and cos() which are
dlsym()ed from libm.so
(sample attached), and an attempt to continue execution seems just hangs the
debugger. For example:
(lldb) attach 17043
Process 17043 stopped
* thread #1, name = 't-dlopen', stop reason = signal SIGSTO
