public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "vi at endrift dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/30221] Negative cache should differentiate failure types
Date: Fri, 17 Mar 2023 23:39:47 +0000	[thread overview]
Message-ID: <bug-30221-10460-1hsU2NoYlO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30221-10460@http.sourceware.org/bugzilla/>

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

--- Comment #11 from Vicki Pfau <vi at endrift dot com> ---
I am using 11.1, but I think part of the problem is that Arch adopted
debuginfod relatively recently and hasn't backfilled packages. I updated my
packages yesterday and it took forever to start gdb today, but I think it was
actually downloading most of those packages so it shouldn't leave negative
cache this time. I don't know how debuginfod federation works either, but I'd
absolutely believe that Arch's server is just slow for one reason or another,
and somehow that's causing issues even though I'm querying the sourceware one
directly.

When I updated gdb a few days ago I did notice that the way information was
presented to the user changed, and it did seem faster, but I'm unsure if that
was just placebo effect due to the fact that it was telling me more information
now.

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

  parent reply	other threads:[~2023-03-17 23:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11  1:32 [Bug debuginfod/30221] New: " vi at endrift dot com
2023-03-13 16:40 ` [Bug debuginfod/30221] " fche at redhat dot com
2023-03-14  1:47 ` vi at endrift dot com
2023-03-17  1:00 ` vi at endrift dot com
2023-03-17  1:08 ` fche at redhat dot com
2023-03-17  1:16 ` vi at endrift dot com
2023-03-17  1:20 ` fche at redhat dot com
2023-03-17  1:28 ` vi at endrift dot com
2023-03-17  1:30 ` vi at endrift dot com
2023-03-17 16:16 ` amerey at redhat dot com
2023-03-17 16:53 ` amerey at redhat dot com
2023-03-17 23:39 ` vi at endrift dot com [this message]
2023-03-24 11:22 ` fche at redhat dot com
2023-04-08 13:29 ` mark at klomp dot org
2023-04-21  2:04 ` fche at redhat dot com

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-30221-10460-1hsU2NoYlO@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@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).