Re: [PATCH] [gdb/tui] Fix crash with debuginfod query

[Andrew Burgess <aburgess@redhat.com>]

Tom Tromey <tom@tromey.com> writes:

>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
>
> Tom> PR tui/31449 reports a SIGFPE when the debuginfod query happens while enabling
> Tom> TUI using the "tui enable" command:
>
> What if we just got rid of the query and debuginfod was either on or off.

I do see some value in having the query.  Users can choose to disable
the feature if they know it's going to end up downloading a bunch of
stuff they don't care about.

But I could imagine maybe flipping things around.  Maybe between GDB
prompts GDB could track how many downloads have been cancelled.  If a
user cancels 2 downloads then GDB could prompt the user at that point:

  Would you like to disable debuginfod for this debug session (y/N)?

That way users only need to take action if they area already hitting
Ctrl-C to cancel downloads.

I'm currently working on updating Aaron's debuginfod patches to add
gdb-index and debug_line section downloading, so I could investigate the
above idea as part of this work.

Thanks,
Andrew