public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29581] New: [gdb/debuginfod] Improve cancelling multiple downloads Date: Sun, 18 Sep 2022 03:25:29 +0000 [thread overview] Message-ID: <bug-29581-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29581 Bug ID: 29581 Summary: [gdb/debuginfod] Improve cancelling multiple downloads Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- When loading an exec into gdb, and libdebuginfod is enabled and available, a single download of debug info is done. But after starting the exec, shares libs will be loaded, and downloads will be issued for each of them, which can be many. If you want to cancel a single download, you press ^C, and gdb will continue with downloading the debuginfo for the next shared lib. But if you want to cancel all following downloads, there's no option but to ^C repeatedly, all he way to the eventual gdb prompt. IWBN if this process was streamlined somewhat. A simple idea to improve on this would be to upon ^C present the user with a choice prompt: ... Download cancelled, continue downloading more debug info (y/n)? ... If n is replied, the downloading of further debug info for other shared libs would be cancelled. The question is what scope that choice would have. We could simply interpret it to mean "set debuginfod enabled off". Alternatively, we could define a download session, and have it be valid for the length of the download session, which could last till for instance the next gdb prompt. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-09-18 3:25 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-18 3:25 vries at gcc dot gnu.org [this message] 2022-09-18 3:25 ` [Bug gdb/29581] " vries at gcc dot gnu.org 2022-09-18 8:34 ` vries at gcc dot gnu.org
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-29581-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: 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).