[Bug corefiles/28636] New: usability suggestions for debuginfod client

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

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

            Bug ID: 28636
           Summary: usability suggestions for debuginfod client
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: corefiles
          Assignee: unassigned at sourceware dot org
          Reporter: fche at redhat dot com
                CC: amerey at redhat dot com, simark at simark dot ca
  Target Milestone: ---

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. 
Programs that use gdb under the covers to do backtracing or whatever now would
start to require an extra gdb command option just to work 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 than "off".

2. displaying "Downloading -0.00 MB separate debug info for ..." is confusing. 
Maybe the files came down too quickly, and the client didn't pass a late enough
progress callback.  (If so, perhaps we could fix that on the debuginfod side,
but I think the code there is good.  GDB should get a notification for the last
download completion packet.)  It'd be better to omit the number, or perhaps
replace it from an actual fstat st_size kind of number if necessary.

3. having "set debuginfod ask" be the default is fine for interactive users -
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?

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