public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gmail 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 16:08:11 +0000	[thread overview]
Message-ID: <bug-29251-4717-VmtnOAHkjn@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 #2 from Martin Sebor <msebor at gmail dot com> ---
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?

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 has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Downloading separate debug info for system-supplied DSO at 0x7ffff7fc8000...
Downloading separate debug info for /lib64/libstdc++.so.6...
Downloading separate debug info for
/home/msebor/.cache/debuginfod_client/455be2588680c3ff57e3a7defe212a13e2efdbd1/debuginfo...
Downloading separate debug info for /lib64/libm.so.6...
Downloading separate debug info for /lib64/libgcc_s.so.1...
Downloading separate debug info for /lib64/libc.so.6...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Downloading separate debug info for /lib64/libz.so.1...
Downloading separate debug info for /lib64/libxml2.so.2...
Downloading separate debug info for /lib64/liblzma.so.5...
[Inferior 1 (process 29469) exited normally]
(gdb)

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

  parent reply	other threads:[~2022-07-05 16:08 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 [this message]
2022-07-05 18:51 ` amerey at redhat dot com
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-VmtnOAHkjn@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).