Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: brobecker@gnat.com, gdb-patches@sources.redhat.com
Subject: Re: Problems with dejagnu and c++ tests...
Date: Wed, 04 Feb 2004 22:49:00 -0000	[thread overview]
Message-ID: <402176E4.5080902@gnu.org> (raw)
In-Reply-To: <20040204223104.7766C4B364@berman.michael-chastain.com>


> ac> Something based on CPP would be more robust, and avoid assumptions such 
> ac> as the target has output and can correctly compile / execute code. 
> ac> Consider what happens when trying to bring up a new GDB+GCC+....
> 
> We're running the test suite.  If gdb_compile does not work,
> or the resulting executables cannot be run, then the test script
> cannot run its tests anyways.

Which would mean that a GCC code-gen bug in malloc, or printf would 
block all ability to run the testsuite :-(  We need to avoid making the 
testsuite fragile.

Andrew



  reply	other threads:[~2004-02-04 22:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04 22:31 Michael Elizabeth Chastain
2004-02-04 22:49 ` Andrew Cagney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-04 23:50 Michael Elizabeth Chastain
2004-02-04 23:55 ` Daniel Jacobowitz
2004-02-04 23:03 Michael Elizabeth Chastain
2004-02-04 23:13 ` Daniel Jacobowitz
2004-02-04 14:01 Michael Elizabeth Chastain
2004-02-04 15:41 ` Andrew Cagney
2004-02-04 12:50 Michael Elizabeth Chastain
2004-02-04 13:20 ` Joel Brobecker
2004-02-04 11:58 Joel Brobecker

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=402176E4.5080902@gnu.org \
    --to=cagney@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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