public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "amerey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/17547] over-eager debuginfo reading
Date: Thu, 05 Jan 2023 01:16:57 +0000	[thread overview]
Message-ID: <bug-17547-4717-HSiZWtmIBG@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17547-4717@http.sourceware.org/bugzilla/>

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

--- Comment #11 from Aaron Merey <amerey at redhat dot com> ---
(In reply to Tom Tromey from comment #10)
> My current work for bug #29942 involves trying to move some gdb work
> into the background, so that when many libraries must be read at
> once, gdb isn't blocking while processing each one.
> 
> The corresponding idea with debuginfod would be to read the .gdb_index
> remotely -- but not even wait for the download to complete before
> setting up the "quick_symbol_functions" object.  Any code trying to
> actually use the index would have to wait for the download to complete,
> but this seems fine to me (assuming the user opts in, like in your patch).
> 
> Perhaps another thing that could be done here is to also trigger a
> background download of the corresponding full files, so they are
> more likely to be available when needed.

These are nice enhancements. I'll try prototyping some basic support
for background downloading and keep an eye out for your PR29942 patch. 

> One funny thing here is that while I've been wanting gdb to move
> towards the DWARF 5 index (see bug #24820), .gdb_index is
> actually more self-contained -- the DWARF 5 index refers to
> .debug_str, and gdb also needs .debug_aranges to work.  So, .gdb_index
> is a little easier for this use.

debuginfod supports the downloading of any ELF sections from a
given file, so we could implement deferred downloads using 
.debug_names and related sections in addition to .gdb_index or
instead of it.

Even if we keep using .gdb_index for this we still may end up
downloading other sections. One issue with deferred downloads that
I'd like to address: commands that require searching debuginfos
for a source file name trigger a mass download of all deferred
debuginfo, since .gdb_index doesn't contain file name information.
Maybe gdb could get this information from downloading
.debug_line/.debug_line_str in addition to .gdb_index.

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

      parent reply	other threads:[~2023-01-05  1:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 15:59 [Bug symtab/17547] New: " tromey at sourceware dot org
2021-05-25 19:15 ` [Bug symtab/17547] " fche at redhat dot com
2021-05-25 19:18 ` cbiesinger at google dot com
2021-05-25 19:19 ` fche at redhat dot com
2021-05-25 19:44 ` simark at simark dot ca
2021-05-25 19:50 ` fche at redhat dot com
2021-05-25 20:21 ` keiths at redhat dot com
2021-05-25 21:24 ` tromey at sourceware dot org
2021-05-26  1:49 ` rfhn.fhbrrjnzeneqpf at noclue dot notk.org
2023-01-01 22:24 ` tromey at sourceware dot org
2023-01-03 23:02 ` amerey at redhat dot com
2023-01-04  2:03 ` tromey at sourceware dot org
2023-01-05  1:16 ` amerey at redhat dot com [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-17547-4717-HSiZWtmIBG@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).