From: Andrew Cagney <ac131313@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA/RFC: dump symtab and psymtab lists
Date: Tue, 15 Apr 2003 15:49:00 -0000 [thread overview]
Message-ID: <3E9C29EE.30409@redhat.com> (raw)
In-Reply-To: <vt2brz8zg5b.fsf@zenia.red-bean.com>
> Andrew Cagney <ac131313@redhat.com> writes:
>
>> > How about 'maint show {,p}symtab'? That's consistent with the main
>> > 'show' command (which displays information about GDB's state), and has
>> > no conflicting precedent.
>
>>
>> No.
>>
>> `show' is for ``showing [and setting] things about the debugger'' -
>> show remote, show debug. Just ignore `set variable ...'.
>>
>> info is for ``showing things about the program being debugged]] - info
>> frame, info registers, info symbols
>>
>> There can be overlap between a `set/show' and `info', but I don't
>> think that occures here.
>
>
> So, you'd prefer "maint info {,p}symtabs", then?
It isn't a question of personal preference. `maint show' would be wrong.
`maint info ....'
appears to be the best fit.
> Existing commands:
> - info sources
> - info functions
Andrew
next prev parent reply other threads:[~2003-04-15 15:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 23:41 Jim Blandy
2003-04-08 7:39 ` Andrew Cagney
2003-04-08 17:52 ` Jim Blandy
2003-04-08 21:13 ` Andrew Cagney
2003-04-09 0:09 ` Jim Blandy
2003-04-10 2:10 ` Andrew Cagney
2003-04-10 20:29 ` Jim Blandy
2003-04-10 21:49 ` Andrew Cagney
2003-04-10 21:56 ` Daniel Jacobowitz
2003-04-12 9:34 ` Eli Zaretskii
2003-04-14 18:43 ` Jim Blandy
2003-04-14 18:52 ` Andrew Cagney
2003-04-14 19:05 ` David Carlton
2003-04-14 19:27 ` Andrew Cagney
2003-04-14 22:41 ` Jim Blandy
2003-04-14 23:40 ` Andrew Cagney
2003-04-15 1:45 ` Jim Blandy
2003-04-15 15:49 ` Andrew Cagney [this message]
2003-04-17 22:09 ` Jim Blandy
2003-04-19 7:40 ` Eli Zaretskii
2003-05-07 21:43 ` Jim Blandy
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=3E9C29EE.30409@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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