From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12506 invoked by alias); 5 Feb 2003 21:30:22 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 12499 invoked from network); 5 Feb 2003 21:30:21 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by 172.16.49.205 with SMTP; 5 Feb 2003 21:30:21 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id h15LUHB10715; Wed, 5 Feb 2003 15:30:17 -0600 Date: Wed, 05 Feb 2003 21:30:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200302052130.h15LUHB10715@duracef.shout.net> To: carlton@math.stanford.edu, fnasser@redhat.com Subject: Clean up gdb.c++ tests for dwarf 1 Cc: gdb@sources.redhat.com X-SW-Source: 2003-02/txt/msg00110.txt.bz2 gdb HEAD%20030205 has loads of this stuff in the C++ test suite: setup_xfail_format "DWARF 1" There are 81 instances of this. Some test scripts have them, and some don't. I'd like to get rid of them and replace them with something more coherent -- or nothing. I see four choices. (1) Just remove these calls to setup_xfail_format. If someone runs the gdb test suite with DWARF 1, the test suite will do its job and give FAIL results for all the C++ tests that do not work with DWARF 1. (2) Change the tests so that each C++ test script reports a single UNSUPPORTED for the whole script (if the debug format is DWARF 1). This requires about five lines of code per script. This cannot be centralized in 'skip_cplus_tests', because the check for the debug format has to happen after the test script has compiled the test program, started gdb, and proceeded to main, so that 'info source' works. (3) Leave the mess alone. (4) Start fixing the DWARF 1 support. I'll start testing DWARF 1 and filing bug reports for the things that don't work. My preference order is (1) - (2) - (3) - (4). What do you think? Michael C