From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 94B583858425; Mon, 29 Nov 2021 19:30:55 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 94B583858425
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/28636] usability suggestions for debuginfod client
Date: Mon, 29 Nov 2021 19:30:55 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: corefiles
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-28636-4717-SiMrv5cv0Y@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28636-4717@http.sourceware.org/bugzilla/>
References: <bug-28636-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Nov 2021 19:30:55 -0000

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

--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
(In reply to Frank Ch. Eigler from comment #0)
> With the recently integrated (gdb) set debuginfod* changes, things look
> different and better in some ways.  Some suggestions for (re)consideratio=
n:
>=20
> 1. defaulting to "set debuginfod off" for batch usage is kind of
> unfortunate.  Programs that use gdb under the covers to do backtracing or
> whatever now would start to require an extra gdb command option just to w=
ork
> as well as gdb 10 did.  I -think- that batch usage of gdb is LESS latency=
 /
> comfort sensitive, so maybe the default should be "on" for them rather th=
an
> "off".

If I understood correctly the original request, defaulting to "no" was for
privacy reasons, making sure to get the user's opt-in before the tool conta=
cts
an external server.  If so, this would be important regardless of whether t=
he
usage is interactive or not.
cessary.

> 3. having "set debuginfod ask" be the default is fine for interactive use=
rs
> - that was the whole point of the patchset.  But answering "y" is purely
> transient, as opposed to one-time.  Could gdb append a setting to its own
> .gdbinit file so that the "y" sticks?

Is the message telling the user to add the comment to their .gdbinit not
enough?

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