Re: tracing broken if target doesn't do disconnected tracing

[Pedro Alves <pedro at codesourcery dot com>]

On Wednesday 07 April 2010 14:32:49, Stan Shebs wrote:
> Yeah, it's been troubling me too.  User-settable variables are GDB's 
> traditional way of instructing GDB about user preferences, but the 
> canned method of phrase construction is too lame to express what is 
> really going on, which is "I prefer that targets to continue tracing 
> after disconnect, whether or not the current target can actually do so". 
> We could use something other than set/show, or invent a better method to 
> produce output - there are other set/shows for which the verbiage is 
> rather contorted.

Hmm, can you expand on what lameness you're referring to exactly?
Is it a technical limitation?

These commands seem to fall in a close category:

(gdb) apropos willingness
set can-use-hw-watchpoints -- Set debugger's willingness to use watchpoint hardware
set displaced-stepping -- Set debugger's willingness to use displaced stepping
show can-use-hw-watchpoints -- Show debugger's willingness to use watchpoint hardware
show displaced-stepping -- Show debugger's willingness to use displaced stepping

Maybe we could follow suit similarly, or instead say something
like: "Show whether GDB prefers to/that/whether ..."

-- 
Pedro Alves