This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]