From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, drow@mvista.com, mec.gnu@mindspring.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc/testsuite] Test GDB on not-so-little core files
Date: Wed, 21 Jan 2004 08:18:00 -0000 [thread overview]
Message-ID: <20040121081729.7A5FC4B359@berman.michael-chastain.com> (raw)
Another thought that might be helpful, or might not:
We could add some environment variables so that the person running
the script could enable specific scripts. Like:
GDB_TEST_SUITE_BIG_CORE
GDB_TEST_SUITE_CPLUS_EXPERIMENTAL
...
GDB_TEST_SUITE_EVERYTHING
The default for all of these would be "off". After some experience
with them, we could take out the environment variable tests.
I was thinking about this for some of the refurbished C++ tests like
member-ptr.exp. This script has lots of interesting non-PASS results
with both g++ and hpacc. Daniel and David would benefit from it while
they are developing, but other people don't want to see all the
non-PASSes because they aren't regressions.
As Andrew likes to say ... thoughts?
Michael C
next reply other threads:[~2004-01-21 8:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 8:18 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-21 4:42 Michael Elizabeth Chastain
2004-01-21 5:23 ` Andrew Cagney
2004-01-14 14:56 Michael Elizabeth Chastain
2004-01-14 15:07 ` Andrew Cagney
2004-01-14 15:16 ` Daniel Jacobowitz
2004-01-14 15:38 ` Andrew Cagney
2004-01-14 15:44 ` Daniel Jacobowitz
2004-01-15 19:09 ` Andrew Cagney
2004-01-15 19:13 ` Daniel Jacobowitz
2004-01-20 22:02 ` Andrew Cagney
2004-01-14 3:11 Michael Elizabeth Chastain
2004-01-14 14:48 ` Andrew Cagney
2004-01-14 2:40 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=20040121081729.7A5FC4B359@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=drow@mvista.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