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: Mon, 04 Jul 2022 20:41:22 +0000 [thread overview] Message-ID: <bug-29251-4717-6Kv8sKcQu4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29251-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29251 Aaron Merey <amerey at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amerey at redhat dot com --- Comment #1 from Aaron Merey <amerey at redhat dot com> --- I was not able to reproduce this using a commit from June 15 (b9b66a3a5740df) or the most recent commit (96c33f79ded35) at the time of writing. I was also not able to reproduce this using gdb-12.1-1.fc35.x86_64. I ran 'gdb opt' with '/bin' as the cwd, like your example output suggests. You mentioned that you've seen this issue before and that it comes and goes seemingly at random. I'm not sure what could be causing this. Maybe there is some weird interaction happening with one of the commands in your .gdbinit, would you be willing to provide that file? Do you have issues with any of gdb's other y/n prompts? The debuginfod first-use prompt uses the same function (nquery) used to implement the following prompt: (gdb) br foo Function "foo" not defined. Make breakpoint pending on future shared library load? (y or [n]) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-04 20:41 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 ` amerey at redhat dot com [this message] 2022-07-05 16:08 ` [Bug gdb/29251] " 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-6Kv8sKcQu4@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).