public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sourceware-bugzilla at totally dot rip" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/29301] New: debuginfod prompt in --batch mode
Date: Wed, 29 Jun 2022 19:34:36 +0000	[thread overview]
Message-ID: <bug-29301-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29301

            Bug ID: 29301
           Summary: debuginfod prompt in --batch mode
           Product: gdb
           Version: 12.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: cli
          Assignee: unassigned at sourceware dot org
          Reporter: sourceware-bugzilla at totally dot rip
  Target Milestone: ---

Since commit 7811fa5995 gdb prompts the user for confirmation to download
debuginfod, even in --batch mode. Now the manpage doesn't state that gdb won't
prompt in batch mode, but still, prompts in batch mode might not be what the
user expects and this might've been implemented this way by mistake.

As a "workaround" -iex 'set debuginfod enabled o(n/ff)' can be used.

See also:
https://bugs.kde.org/show_bug.cgi?id=454063
https://sourceware.org/bugzilla/show_bug.cgi?id=27532

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

             reply	other threads:[~2022-06-29 19:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 19:34 sourceware-bugzilla at totally dot rip [this message]
2022-07-04 22:13 ` [Bug cli/29301] " amerey at redhat dot com
2022-07-15 21:45 ` 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-29301-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).