Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA/RFC: dump symtab and psymtab lists
Date: Thu, 10 Apr 2003 21:56:00 -0000	[thread overview]
Message-ID: <20030410215555.GA31482@nevyn.them.org> (raw)
In-Reply-To: <3E95E6D7.6030207@redhat.com>

On Thu, Apr 10, 2003 at 05:49:11PM -0400, Andrew Cagney wrote:
> >Andrew Cagney <ac131313@redhat.com> writes:
> >
> >>> Could you suggest a way I can provide the utility I need, without
> >>> introducing an unnecessary inconsistency?  I'm not sure what you're
> >>> looking for.
> >
> >>
> >>Some level of consistency with the rest of the CLI (which isn't easy).
> >>
> >
> >>> How about 'maint print symtabs [-matching REGEXP] [outfile]'?
> >
> >>
> >>maint grep <table> <expression>
> >>maint search <table> <expression>
> >
> >
> >Okay, here's a revised patch that calls them "maint list {,p}symtab".
> 
> Unfortunatly, there is `(gdb) list' command, so one would expect a 
> certain level of correspondance between `(gdb) list' and `(gdb maint 
> list'.  This is like `(gdb) info breakpoints' vs `(gdb) maint info 
> breakpoints'.
> 
> This also rules out my `maint search' suggestion :-(
> `maint query <db> <query>'?
> 
> >Perhaps commands that produce so much output that they need to be able
> >to send it to a file should be renamed to "maint dump"?
> 
> True.

I think this is an excellent idea.

It does point out that expecting the correspondence may be unwise.  We
already have both print and dump.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-04-10 21:56 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 [this message]
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
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=20030410215555.GA31482@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=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