Re: [PATCH 0/3] Improve debug output support in gdbserver

[Tom Tromey <tom@tromey.com>]

>>>>> "Andrew" == Andrew Burgess <aburgess@redhat.com> writes:

Andrew> QUESTION: How would folk feel if I was super aggressive and removed
Andrew> these older flags?  In theory these flags are only used for debugging
Andrew> gdbserver itself, but who knows, right?

I think it would be completely fine.  I think it would be a bad idea for
us to promise that debug flags won't change, and the current approach in
gdbserver isn't really all that great.

Andrew> And on the monitor command side, we now support:

Andrew>   (gdb) monitor set debug COMPONENT 1
Andrew>   (gdb) monitor set debug COMPONENT 0

Andrew> to enable and disable debug for COMPONENT.  Where COMPONENT is again,
Andrew> 'threads', 'remote', and 'event-loop'.  Again, I've retained:

Andrew>   (gdb) set debug 1
Andrew>   (gdb) set debug 0

Andrew> which is equivalent to 'set debug threads 1' or 'set debug threads 0'.
Andrew> And I've also retained the legacy:

Andrew>   (gdb) set remote-debug 1
Andrew>   (gdb) set remote-debug 0
Andrew>   (gdb) set event-loop-debug 1
Andrew>   (gdb) set event-loop-debug 0
  
Andrew> QUESTION: As with the command line, how would people feel if I ripped
Andrew> out all of the legacy support and required folks to move to the newer
Andrew> command set?

I think this would also be fine.

Tom