From: Tom Tromey <tom@tromey.com>
To: Aaron Merey <amerey@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
Aaron Merey via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC][PATCH] gdb/debuginfod: Support on-demand downloading of debuginfo
Date: Thu, 12 Jan 2023 20:53:11 -0700 [thread overview]
Message-ID: <877cxr3xaw.fsf@tromey.com> (raw)
In-Reply-To: <CAJDtP-QTogs7apCkTpQPkt4trcstXWGhE=uh2R5AtpyT_nwrhQ@mail.gmail.com> (Aaron Merey's message of "Thu, 12 Jan 2023 19:49:56 -0500")
>>>>> "Aaron" == Aaron Merey <amerey@redhat.com> writes:
Aaron> Currently if the index downloads successfully but the debuginfo download
Aaron> fails, the usual "Download failed" message is printed and it indicates
Aaron> that gdb will continue without that library's debuginfo.
Yeah, this seems fine to me.
Aaron> So far I
Aaron> haven't seen any issues in these cases but making use of "noshared"
Aaron> is a good idea.
If it works :). It would probably be useful for users if we had some
way for them to say "try again to find some debuginfo". But maybe
noshared+sharedlibrary works enough for that, I am not sure.
Tom
prev parent reply other threads:[~2023-01-13 3:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 2:24 Aaron Merey
2022-10-21 16:44 ` [PING][RFC PATCH] " Aaron Merey
2022-11-04 22:34 ` [PATCH] " Aaron Merey
2022-11-18 20:33 ` [PING*3][RFC PATCH] " Aaron Merey
2023-01-03 21:32 ` [PING*4][RFC " Aaron Merey
2023-01-11 21:25 ` [RFC][PATCH] " Tom Tromey
2023-01-13 0:49 ` Aaron Merey
2023-01-13 3:53 ` Tom Tromey [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=877cxr3xaw.fsf@tromey.com \
--to=tom@tromey.com \
--cc=amerey@redhat.com \
--cc=gdb-patches@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).