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 gdb/29251] gdb stuck asking to enable debuginfod Date: Tue, 05 Jul 2022 18:51:55 +0000 [thread overview] Message-ID: <bug-29251-4717-YU6L8EhZL6@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29251-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29251 --- Comment #3 from Aaron Merey <amerey at redhat dot com> --- (In reply to Martin Sebor from comment #2) > I can't reproduce with either of those today either (my output is below). > Could it be triggered by the site being down or unreachable? If there was a network error you'd see something like: Downloading separate debug info for /lib64/libc.so.6... Download failed: No route to host. Continuing without debug info for /lib64/libc.so.6. The logic for the y/n prompt is self-contained in gdb and does not depend on the network at all so it would be unaffected by these kinds of errors. > A separate question is why it's downloading these files again? I imagine it > must have downloaded all of them at some point before, and I haven't updated > my machine in months. Debuginfod's cache of downloaded files is periodically cleaned and, by default, files that have gone unaccessed for at least a week are deleted during a cleaning pass. The cleaning frequency and time limit for unaccessed files can be controlled by the cache_clean_interval_s and max_unused_age_s files in the cache. See 'man debuginfod' for more info. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-05 18:51 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-15 15:42 [Bug gdb/29251] New: " msebor at gmail dot com 2022-07-04 20:41 ` [Bug gdb/29251] " amerey at redhat dot com 2022-07-05 16:08 ` msebor at gmail dot com 2022-07-05 18:51 ` amerey at redhat dot com [this message] 2023-01-31 16:34 ` chad.cassady at gmail dot com 2023-02-01 0:03 ` amerey 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-29251-4717-YU6L8EhZL6@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: linkBe 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).