From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12898 invoked by alias); 12 Sep 2003 22:24:30 -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 12891 invoked from network); 12 Sep 2003 22:24:30 -0000 Received: from unknown (HELO concert.shout.net) (204.253.184.25) by sources.redhat.com with SMTP; 12 Sep 2003 22:24:30 -0000 Received: from duracef.shout.net (duracef.shout.net [204.253.184.12]) by concert.shout.net (8.12.9/8.12.9) with ESMTP id h8CMOS9Q001817; Fri, 12 Sep 2003 17:24:28 -0500 Received: from duracef.shout.net (localhost [127.0.0.1]) by duracef.shout.net (8.12.9/8.12.9) with ESMTP id h8CMOSHK027466; Fri, 12 Sep 2003 17:24:28 -0500 Received: (from mec@localhost) by duracef.shout.net (8.12.9/8.12.9/Submit) id h8CMOSkI027465; Fri, 12 Sep 2003 18:24:28 -0400 Date: Fri, 12 Sep 2003 22:24:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200309122224.h8CMOSkI027465@duracef.shout.net> To: cgf@redhat.com, gdb@sources.redhat.com Subject: Re: gcc HEAD bad stabs (?) X-SW-Source: 2003-09/txt/msg00174.txt.bz2 cgf> "again"? When did it stop? Okay, "again" is not quite what I meant to say. I really meant: "once again, gcc HEAD has a new bug". I'm starting to expect 1-2 of these per week. cgf> Things seem to be getting worse and worse. They are. I'm opening bugs against gcc HEAD faster than the gcc people are closing them. And I still have several regressions left over from the April-June period when I wasn't around. As far as I can see, the only feedback loop for gcc debug info changes is me running the test suite. Ideas for improving this welcomed. Maybe I should set up a separate test bed and spin it 1-2 times per day with gcc HEAD, binutils 2.14, gdb 5.3.91. Michael C