From: Michael Chastain <mec.gnu@mindspring.com>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [obish] Zap m* methods
Date: Tue, 10 Aug 2004 23:14:00 -0000 [thread overview]
Message-ID: <411956E5.nailAQA11S3HG@mindspring.com> (raw)
In-Reply-To: <4119547E.8010405@gnu.org>
Andrew Cagney <cagney@gnu.org> wrote:
> Ok, not so obish then, can you, I'm mid way through testing step.
Yeah, I'll pick it up.
Maybe I could say
-re "init_malloc" {
# removed from gdb HEAD 2004-08-10
fail "old gdb"
set command "next"
}
I'll play with it a bit.
Got a lot of processes on my run queue too.
Michael C
prev parent reply other threads:[~2004-08-10 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 22:38 Andrew Cagney
2004-08-10 22:59 ` Michael Chastain
2004-08-10 23:04 ` Andrew Cagney
2004-08-10 23:14 ` Michael Chastain [this message]
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=411956E5.nailAQA11S3HG@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--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