[RFC] Toogle debug flags in gdbserver

[RFC] Toogle debug flags in gdbserver

[Markus Deuling]

Hi,

there are two debug flags in gdbserver:

* debug_threads
* remote_debug

Both are '0' as default. 'remote_debug' may be toogled by a 'd' packet. The doc says 'Don't use this packet, define a general set packet...'.

I think it would be a good idea to have the possibility to switch on/off these two debug flags in the gdbserver without re-compiling it.

The idea is to define two new packets 'qDebugThread' and 'qDebugRemote' and connect it to two new
'set debug' commands.

'set debug remote_thread <value>' with value={0,1} sends 'qDebugThread:<value>' if remote connection is available
'set debug remote_remote <value>' with value={0,1} sends 'qDebugRemote:<value>' if remote connection is available

Reply to these package would be 'OK' if applied. An older gdbversion without qDebug* support would reply '0'
(default response in server.c:handle_query() if it gets an unsupported qPacket).


What do you think of this idea? If I implement it, I would think it's a good idea to remove support for 'd' packets, isn't it ?



Regards,
Markus

-- 
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com 

Re: [RFC] Toogle debug flags in gdbserver

[Daniel Jacobowitz]

On Thu, Jan 18, 2007 at 12:54:10PM +0100, Markus Deuling wrote:
> The idea is to define two new packets 'qDebugThread' and 'qDebugRemote' and 
> connect it to two new
> 'set debug' commands.

RDA uses "monitor" commands to toggle debug flags; I think that's
probably simpler.

-- 
Daniel Jacobowitz
CodeSourcery

Re: [RFC] Toogle debug flags in gdbserver

[Markus Deuling]

Hi Daniel,

Daniel Jacobowitz schrieb:
> On Thu, Jan 18, 2007 at 12:54:10PM +0100, Markus Deuling wrote:
>> The idea is to define two new packets 'qDebugThread' and 'qDebugRemote' and 
>> connect it to two new
>> 'set debug' commands.
> 
> RDA uses "monitor" commands to toggle debug flags; I think that's
> probably simpler.
> 

thank you for your hint. But I think I oversee s.th. The monitor cmd seems not to 
work for me.

How can I set "debug_threads" eg in linux-low.c to 1 with the 'monitor' command ? The 
only way I currently see is to toggle 'remote_debug' with a 'd' Packet.


Regards,
Markus

-- 
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com