From: Aaron Merey <amerey@redhat.com>
To: Patrick Monnerat <patrick@monnerat.net>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH v3] gdb: Improve debuginfod progress updates
Date: Thu, 17 Feb 2022 11:06:37 -0500 [thread overview]
Message-ID: <CAJDtP-SECoCn3ODGhGuMB-m3haE3rVjcGCqsV_p8cd-gnRtNPA@mail.gmail.com> (raw)
In-Reply-To: <5e6194e4-3a83-e169-0c9a-5858c993bf59@monnerat.net>
On Wed, Feb 16, 2022 at 5:38 AM Patrick Monnerat <patrick@monnerat.net> wrote:
> > I've experienced at least one case where percent was > 1.0. I haven't
> > been able to reproduce it because it seemed to coincide with a network
> > hiccup.
> Very strange! TCP is supposed to guarantee no duplicate data reception.
> If this really occurs, debuginfo data are probably corrupted too!
I have not seen any corrupt debuginfo acquired from debuginfod.
Each time debuginfo is downloaded there is a check to make sure it
has the expected build-id. The integrity of the debuginfo is also verified
using the CRC in the parent file's .gnu_debuglink section.
Aaron
next prev parent reply other threads:[~2022-02-17 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 0:58 [PATCH v2] gdb/debuginfod: Rework " Aaron Merey
2022-02-09 2:25 ` [PATCH v3] gdb: Improve debuginfod " Aaron Merey
2022-02-14 0:56 ` Patrick Monnerat
2022-02-16 2:09 ` Aaron Merey
2022-02-16 10:38 ` Patrick Monnerat
2022-02-17 16:06 ` Aaron Merey [this message]
2022-03-04 18:15 ` Tom Tromey
2022-03-09 1:26 ` Aaron Merey
2022-03-18 19:23 ` Tom Tromey
2022-03-22 0:27 ` Aaron Merey
2022-04-07 14:54 ` Tom Tromey
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=CAJDtP-SECoCn3ODGhGuMB-m3haE3rVjcGCqsV_p8cd-gnRtNPA@mail.gmail.com \
--to=amerey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=patrick@monnerat.net \
--cc=tom@tromey.com \
/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).