Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>,
	Kevin Buettner <kevinb@cygnus.com>,
	jason-swarelist@molenda.com, gdb-patches@sources.redhat.com,
	tromey@cygnus.com
Subject: Re: [RFA] Version 2 of patch to add 'maint profile-gdb' command
Date: Mon, 24 Sep 2001 11:02:00 -0000	[thread overview]
Message-ID: <3BAF7465.C3DEE192@cygnus.com> (raw)
In-Reply-To: <3BAD1A02.1000702@cygnus.com>

Andrew Cagney wrote:
> 
> > On Wed, 19 Sep 2001, Kevin Buettner wrote:
> >
> >
> >> I like having the maintenance commands all lumped under "maint".  That
> >> way I can use tab completion to see all of the maintenance related commands
> >> when I do
> >>
> >> (gdb) maint <TAB>
> >>
> >> I think a set/show would be useful for some activities; couldn't
> >> we add "maint set ..." and "maint show ..."  ?
> >
> >
> > That seems to be a good idea, IMHO.
> 
> Turns out there is already a ``maint info'' so a ``maint set/show''
> makes good sense.  Try the attached.
> 

Nice.

> Jason, I think it is pretty clear where to add the profiling bit :-)
> Eli, if the doco entry is going in gdb.texinfo, can you suggest where?
> Fernando, is this part ok?
> 

Yes, sure.

P.S.: There are some maint commands that should be maint set/show in 
the arm rdi thing.  Can you add fixing those to the TODO list, please?  


-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  parent reply	other threads:[~2001-09-24 11:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.SUN.3.91.1010920101719.3922A-100000@is>
     [not found] ` <3BAD1A02.1000702@cygnus.com>
2001-09-23  6:07   ` Eli Zaretskii
2001-09-24 11:02   ` Fernando Nasser [this message]
2001-09-24 12:06     ` Andrew Cagney
2001-09-24 19:39     ` Andrew Cagney
2001-09-10  0:30 [RFA] " Jason Molenda
2001-09-10  8:48 ` Andrew Cagney
2001-09-10 11:52   ` Jason Molenda
2001-09-12 11:43     ` Andrew Cagney
2001-09-16 17:45       ` [RFA] Version 2 of " Jason Molenda
     [not found]         ` <200109170536.HAA21988@is.elta.co.il>
2001-09-17 15:08           ` Michael Snyder
2001-09-17 22:43           ` Andrew Cagney
2001-09-17 23:59             ` Eli Zaretskii
2001-09-24 13:33               ` Jason Molenda
2001-09-24 14:41                 ` Andrew Cagney
2001-09-24 14:58                   ` Eli Zaretskii
2001-09-24 15:13                     ` Andrew Cagney
2001-09-24 14:53                 ` Eli Zaretskii
2001-09-17 22:39         ` Andrew Cagney
2001-09-18 17:52           ` Fernando Nasser
2001-09-18 17:56             ` Andrew Cagney
2001-09-19  7:11               ` Fernando Nasser
2001-09-19  7:28                 ` Eli Zaretskii
2001-09-19  9:29                   ` Fernando Nasser
2001-09-19 11:30                     ` Eli Zaretskii
2001-09-19 11:41                     ` Andrew Cagney
2001-09-19 11:53                     ` Kevin Buettner

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=3BAF7465.C3DEE192@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jason-swarelist@molenda.com \
    --cc=kevinb@cygnus.com \
    --cc=tromey@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