Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: gdb-patches@sources.redhat.com, cagney@gnu.org
Subject: Re: [obish] Zap m* methods
Date: Tue, 10 Aug 2004 22:59:00 -0000	[thread overview]
Message-ID: <4119521E.nailAPE13HNES@mindspring.com> (raw)
In-Reply-To: <41194E61.2050801@gnu.org>

Actually, I would like to keep the init_malloc in selftest.exp.

Here's why.  When I look for regressions in gdb, I use the current
test suite with the old gdb and the new gdb.  So it helps if the
current test suite doesn't do "default { fail; return }" when I
run it with gdb 6.2.  I can live with the "fail" but it's the
"return" that kills me, by killing the rest of selftest.exp.

This is going to get a bit more important than usual because test suites
before the current test suite don't work well with gcc 3.5 prerelease.
(Current test suite still has problems but I'm working on them).

Andrew, okay with you if I put the init_malloc back?

Michael C


  reply	other threads:[~2004-08-10 22:59 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 [this message]
2004-08-10 23:04   ` Andrew Cagney
2004-08-10 23:14     ` Michael Chastain

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=4119521E.nailAPE13HNES@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