From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18581 invoked by alias); 21 Jan 2004 08:18:05 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 18551 invoked from network); 21 Jan 2004 08:17:54 -0000 Received: from unknown (HELO blount.mail.mindspring.net) (207.69.200.226) by sources.redhat.com with SMTP; 21 Jan 2004 08:17:55 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by blount.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1AjDY6-0002n6-00; Wed, 21 Jan 2004 03:17:18 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 7A5FC4B359; Wed, 21 Jan 2004 03:17:29 -0500 (EST) To: cagney@gnu.org, drow@mvista.com, mec.gnu@mindspring.com Subject: Re: [patch/rfc/testsuite] Test GDB on not-so-little core files Cc: gdb-patches@sources.redhat.com Message-Id: <20040121081729.7A5FC4B359@berman.michael-chastain.com> Date: Wed, 21 Jan 2004 08:18:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-01/txt/msg00575.txt.bz2 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