Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Markus Deuling <deuling@de.ibm.com>
To: GDB Discuss <gdb@sources.redhat.com>
Subject: [RFC] Toogle debug flags in gdbserver
Date: Thu, 18 Jan 2007 11:54:00 -0000	[thread overview]
Message-ID: <45AF5FE2.1050101@de.ibm.com> (raw)

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 


             reply	other threads:[~2007-01-18 11:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 11:54 Markus Deuling [this message]
2007-01-18 16:31 ` Daniel Jacobowitz
2007-01-19 13:51   ` Markus Deuling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45AF5FE2.1050101@de.ibm.com \
    --to=deuling@de.ibm.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox