From: Andrew Cagney <ac131313@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [rfc] more findvar harvard fixes
Date: Sat, 22 Sep 2001 14:11:00 -0000 [thread overview]
Message-ID: <3BACFE82.7020104@cygnus.com> (raw)
Hello,
The attached patch follows through a few harvard architecture problems
Nick Duffek and Jim Blandy worked though in the recent thread:
http://sources.redhat.com/ml/gdb-patches/2001-07/msg00382.html
Given I think I'm just finishing these changes, I think this is pretty
obvious so I'll check it in in a few days.
Look ok to people.
Andrew
From ac131313@cygnus.com Sat Sep 22 16:09:00 2001
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Kevin Buettner <kevinb@cygnus.com>, Fernando Nasser <fnasser@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: Sat, 22 Sep 2001 16:09:00 -0000
Message-id: <3BAD1A02.1000702@cygnus.com>
References: <Pine.SUN.3.91.1010920101719.3922A-100000@is>
X-SW-Source: 2001-09/msg00304.html
Content-length: 692
> 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.
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?
Andrew
next reply other threads:[~2001-09-22 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-22 14:11 Andrew Cagney [this message]
2001-09-24 11:22 ` Michael Snyder
2001-09-24 12:56 ` Andrew Cagney
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=3BACFE82.7020104@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.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