[Bug corefiles/28636] usability suggestions for debuginfod client

["fche at redhat dot com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> ---
(In reply to Simon Marchi from comment #1)
> (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)consideration:
> > 
> > 1. defaulting to "set debuginfod off" for batch usage is kind of
> > unfortunate. [...]
> 
> 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
> contacts an external server.  If so, this would be important regardless of
> whether the usage is interactive or not.

The angle I'm focusing on here is that gdb is used by non-human-users to do
batch work.  I -suspect- that much? most? gdb -batch usage might in fact be
performed by automated tooling rather than humans.

(Rather than privacy, the motivation for this was more security, in case a
user might be concerned about downloading corrupted data.  There is
hardly any private information sent to a server.  Not sure this matters for
this topic.)


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

IMHO it'd be better if gdb were to do that.  Is there any precedent for
persistent settings like this?

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