[Bug symtab/17547] over-eager debuginfo reading

["tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17547

--- Comment #8 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Frank Ch. Eigler from comment #3)
> (In reply to Christian Biesinger from comment #2)
> > backtrace needs debug data for stack unwinding & showing function names (and
> > arguments)
> 
> Certainly, but not for ALL solibs, just those implicated in an actual stack
> frame.

gdb can do some weird stuff for type lookups, so this would need
a bit of careful attention.

Anyway I was wondering recently why gdb isn't using the shared library
memory map to decide which objfiles to search.  That is, surely if
a PC is in some mapped range, then the debuginfo for that function
will come from the corresponding .so.

There's a bunch of loops like:

  for (objfile *objfile : current_program_space->objfiles ())
    {
      struct compunit_symtab *cust
        = objfile->find_pc_sect_compunit_symtab (msymbol, pc, section, 0);
      if (cust)
        return;
    }

... that could then be simplified.  On the branch I'm working on
(see bug #29942), this wouldn't improve downloads of debuginfo,
but would improve parsing wait times.

-- 
You are receiving this mail because:
You are on the CC list for the bug.