From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [rfa] clean up output of "info set" command.
Date: Fri, 11 Feb 2011 20:53:00 -0000 [thread overview]
Message-ID: <4D55A1A4.5020208@vmware.com> (raw)
In-Reply-To: <201102112042.45033.pedro@codesourcery.com>
Pedro Alves wrote:
> On Friday 11 February 2011 20:19:52, Michael Snyder wrote:
>> "info set" is meant to show the state of all "set"-able
>> debugger state variables, but it really executes each and
>> every "show" command in alphabetical order.
>>
>> Several of these commands (notably "copying" and "warranty")
>> have no corresponding "set" command, are not "set"-able, and
>> produce a lot of output. Especially "show copying" which
>> produces pages and pages of output.
>
> Isn't there a property of the command we could check
> instead of hardcoding specific command names?
I'm open to suggestions. The only property I can think of is that
there is no corresponding entry in "setlist". I could search
setlist every time...
>> This patch excludes "copying", "warranty", and "version" from
>> the output of "info set'.
>
next prev parent reply other threads:[~2011-02-11 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 20:20 Michael Snyder
2011-02-11 20:42 ` Pedro Alves
2011-02-11 20:53 ` Michael Snyder [this message]
2011-02-11 21:17 ` Tom Tromey
2011-02-11 23:33 ` Pedro Alves
2011-02-12 0:01 ` Michael Snyder
2011-02-12 0:08 ` Michael Snyder
2011-02-12 1:30 ` Michael Snyder
2011-02-12 7:55 ` Eli Zaretskii
2011-02-15 2:03 ` Michael Snyder
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=4D55A1A4.5020208@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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