This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [patch/rfc/testsuite] Test GDB on not-so-little core files
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: cagney at gnu dot org, drow at mvista dot com, mec dot gnu at mindspring dot com
- Cc: gdb-patches at sources dot redhat dot com
- Date: Wed, 21 Jan 2004 03:17:29 -0500 (EST)
- Subject: Re: [patch/rfc/testsuite] Test GDB on not-so-little core files
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