On Mon, Jun 4, 2012 at 8:03 AM, Pedro Alves <palves@redhat.com> wrote:
> On 06/04/2012 05:06 AM, Doug Evans wrote:
>
>> GDB's symbol support is a mess (IMO), and I wanted
>> a name and usage to restrict it to the task at hand.  Anything more
>> general and I was pretty sure this patch would get bogged down.
>
>
> That'd be a bit beyond what I requested.  ;-)
>
>> Later on I want to revamp the symbol API, but I don't want this patch
>> tied down by that.
>
>
> Certainly.  That'd clearly need to be a separate change.
>
>> (For example, I don't want to bubble up the semantics of
>> demangle_for_lookup to the caller of this function.   Here we have an
>> msymbol, we know we have a mangled name.  If you want, I can go with
>> lookup_symbol_in_objfile but rename it to
>> lookup_symbol_in_objfile_from_linkage_name or some such.)
>
>
> That'd be fine with me.  Thanks.

Here is what I checked in.

2012-06-18  Doug Evans  <dje@google.com>

        * symtab.h (minimal_symbol): New member created_by_gdb.
        * elfread.c (elf_symtab_read): Set created_by_gdb for @plt minsym
        created by gdb.
        * symtab.c (lookup_symbol_in_objfile_from_linkage_name): New function.
        (search_symbols): Call it instead of lookup_symbol.
        Skip symbols created by gdb.  Only scan minsyms if nfiles == 0.

        testsuite:
        * gdb.base/info-fun.exp: New file.
        * gdb.base/info-fun.c: New file.
        * gdb.base/info-fun-solib.c: New file.