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] New: gdb stuck asking to enable debuginfod
Date: Wed, 15 Jun 2022 15:42:12 +0000 [thread overview]
Message-ID: <bug-29251-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29251
Bug ID: 29251
Summary: gdb stuck asking to enable debuginfod
Product: gdb
Version: 11.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: msebor at gmail dot com
Target Milestone: ---
Between last night and today with no changes to my system that I know of my GDB
stopped working with the output below (I've been using GDB trunk to get around
a bug; the output below is with a fresh build of the latest GDB trunk as of
today). The first 14 "Please answer..." prompts appear before I have a chance
to enter anything. The rest are in response to typing n, that GDB doesn't seem
to understand. I've seen this problem before but it went away on its own until
today. Adding `set debuginfod enabled off` to .gdbinit avoids it, but that
seems like a workaround.
Current directory is /bin/
GNU gdb (GDB) 13.0.50.20220615-git
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /bin/opt...
This GDB supports auto-downloading debuginfo from the following URLs:
<https://debuginfod.fedoraproject.org/>
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) Please answer y or [n].
Enable debuginfod for this session? (y or [n]) n
Please answer y or [n].
Enable debuginfod for this session? (y or [n]) n
Please answer y or [n].
Enable debuginfod for this session? (y or [n]) n
Please answer y or [n].
Enable debuginfod for this session? (y or [n]) n
Please answer y or [n].
Enable debuginfod for this session? (y or [n])
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-06-15 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 15:42 msebor at gmail dot com [this message]
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
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@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).