Re: [PATCH 00/11] Fixing GNU ifunc support

[Pedro Alves <palves at redhat dot com>]

On 03/12/2018 11:16 AM, Alan Hayward wrote:
> 
> 
>> On 9 Mar 2018, at 21:18, Pedro Alves <palves@redhat.com> wrote:
>>
>> On 03/09/2018 09:16 PM, Pedro Alves wrote:
>>
>>> Pedro Alves (11):
>>>  eval.c: reverse minsym and sym
>>>  Fix breakpoints in ifunc after inferior resolved it (@got.plt symbol
>>>    creation)
>>>  Fix calling ifunc functions when resolver has debug info and different
>>>    name
>>>  Calling ifunc functions when target has no debug info but resolver has
>>>  Calling ifunc functions when resolver has debug info, user symbol same
>>>    name
>>>  Fix setting breakpoints on ifunc functions after they're already
>>>    resolved
>>>  Breakpoints, don't skip prologue of ifunc resolvers with debug info
>>>  Eliminate find_pc_partial_function_gnu_ifunc
>>>  Factor out minsym_found/find_function_start_sal overload
>>>  Extend GNU ifunc testcases
>>>  Fix resolving GNU ifunc bp locations when inferior runs resolver
>>
>> As always, I forgot to say that I pushed this to the
>> "users/palves/ifunc" branch on sourceware.org.
>>
> 
> I was using your branch to try a few things, and debugging gdb gave me a segfault:
> 
> $ ./gdb/gdb ./gdb/gdb
> 
> (gdb) b amd64_push_dummy_call
> Segmentation fault (core dumped)

Thanks, I can reproduce this.  Looks like the sal has a symtab, but sal.objfile
is left NULL.

Pedro Alves