From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15027 invoked by alias); 5 May 2004 05:03:45 -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 15015 invoked from network); 5 May 2004 05:03:44 -0000 Received: from unknown (HELO smtp10.atl.mindspring.net) (207.69.200.246) by sources.redhat.com with SMTP; 5 May 2004 05:03:44 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp10.atl.mindspring.net with esmtp (Exim 3.33 #1) id 1BLEXw-0005T9-00; Wed, 05 May 2004 01:02:16 -0400 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 1CF744B104; Wed, 5 May 2004 01:02:12 -0400 (EDT) To: jkj@sco.com, shebs@apple.com Subject: Re: Phasing out Dwarf 1? Cc: cagney@gnu.org, ezannoni@redhat.com, gdb@sources.redhat.com, jimb@redhat.com, mec.gnu@mindspring.com, nathanw@wasabisystems.com Message-Id: <20040505050212.1CF744B104@berman.michael-chastain.com> Date: Wed, 05 May 2004 05:03:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-05/txt/msg00030.txt.bz2 Stan Shebs writes: > But how is it going to get tested? Experience shows that untested parts > of GDB bitrot pretty quickly, and without any volunteers to let us know > when things break and/or fix them when they do, the claim of support > is just misleading to users. On this subject, the last time I tried dwarf-1 with the gdb test suite, I got 46 ERROR, 39 UNRESOLVED, and 3463 FAIL. This was in February 2003. http://sources.redhat.com/ml/gdb-patches/2003-02/msg00293.html IIRC, the test suite took about nine hours to run, compared to fifteen minutes for dwarf-2 or stabs+. I don't know if this is systemic failure in the test suite or systemic failure in gdb. Michael C