Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@cgsoftware.com>
To: gdb-patches@sourceware.cygnus.com
Subject: [PATCH]: add set/show debug, move gdb debugging flags into it
Date: Mon, 13 Mar 2000 09:04:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.10003130852170.6968-200000@localhost.localdomain> (raw)

Attached is a patch to add "set debug" and "show debug", and move the gdb
debugging stuff (targetdebug,expressiondebug,etc) into those lists.

I renamed targetdebug,expressiondebug,etc (all the debug settings i
moved), to remove the "debug" from their name, so you do "set debug target
1" rather than "set debug targetdebug 1".

The new command lists are named setdebuglist/showdebuglist, and are in
command.c.
I put set_debug and show_debug into command.c, for lack of a better place.
The point of all this is to make it much easier to see what debugging
flags you can set for GDB, and what they were set to. It also declutters
the set list.
I also enabled monitordebug, since it said int he comment it was waiting
for "set debug".

I have no idea who needs to approve this, since it touches a bunch of
stuff, but is only related to one domain so to speak.

I'm working on a changelog entry,  i wanted to get comments first.

Example of what you get with the patch installed:
(gdb) help set debug
Generic command for setting gdb debugging flags
List of set debug subcommands:
set debug arch -- Set architecture debugging
set debug event -- Set event debugging
set debug expression -- Set expression debugging
set debug remote -- Set debugging of remote protocol
set debug serial -- Set serial debugging
set debug target -- Set target debugging
set debug varobj -- Set varobj debugging
Type "help set debug" followed by set debug subcommand name for full
documentation.
Command name abbreviations are allowed if unambiguous.
(gdb)

(gdb) help show debug
Generic command for showing gdb debugging flags
List of show debug subcommands:
show debug arch -- Show architecture debugging
show debug event -- Show event debugging
show debug expression -- Show expression debugging
show debug remote -- Show debugging of remote protocol
show debug serial -- Show serial debugging
show debug target -- Show target debugging
show debug varobj -- Show varobj debugging
Type "help show debug" followed by show debug subcommand name for full
documenta
tion.
Command name abbreviations are allowed if unambiguous.
(gdb)
(gdb) show debug
arch:  Architecture debugging is 0.
event:  Event debugging is 0.
expression:  Expression debugging is 0.
remote:  Debugging of remote protocol is 0.
serial:  Serial debugging is 0.
target:  Target debugging is 0.
varobj:  Varobj debugging is 0.
(gdb) set debug
"set debug" must be followed by the name of a print subcommand.
List of set debug subcommands:
set debug arch -- Set architecture debugging
set debug event -- Set event debugging
set debug expression -- Set expression debugging
set debug remote -- Set debugging of remote protocol
set debug serial -- Set serial debugging
set debug target -- Set target debugging
set debug varobj -- Set varobj debugging
Type "help set debug" followed by set debug subcommand name for full
documentati
on.
Command name abbreviations are allowed if unambiguous.
(gdb)


             reply	other threads:[~2000-03-13  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-13  9:04 Daniel Berlin [this message]
2000-04-01  0:00 ` Fernando Nasser
     [not found] ` <200003150919.EAA29966@indy.delorie.com>
     [not found]   ` <r9dctixc.fsf@dan.resnet.rochester.edu>
     [not found]     ` <200003151430.JAA01149@indy.delorie.com>
     [not found]       ` <38CFAE9E.39D1C081@redhat.com>
     [not found]         ` <38CFB57A.1900@cygnus.com>
2000-04-01  0:00           ` Fernando Nasser
2000-03-15  8:39             ` Fernando Nasser

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=Pine.LNX.4.10.10003130852170.6968-200000@localhost.localdomain \
    --to=dan@cgsoftware.com \
    --cc=gdb-patches@sourceware.cygnus.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