From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8048 invoked by alias); 20 Nov 2002 18:43:43 -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 8040 invoked from network); 20 Nov 2002 18:43:42 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 20 Nov 2002 18:43:42 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 8CB41D2CE1; Wed, 20 Nov 2002 10:43:42 -0800 (PST) Date: Wed, 20 Nov 2002 10:43:00 -0000 From: Joel Brobecker To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: [5.3] What's the hold up? Message-ID: <20021120184342.GR1259@gnat.com> References: <3DDBCB76.50205@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DDBCB76.50205@redhat.com> User-Agent: Mutt/1.4i X-SW-Source: 2002-11/txt/msg00279.txt.bz2 > 676 gdb analyzed high unassigned Alpha OSF1, gcc, internal GDB error in > mdebugread > 708 gdb open high unassigned Can't build 5.3 branch (and probably trunk). [...] > Of most concern are 708 and 676. They both indicate something failing the: > > ./configure > make > ./gdb/gdb ./gdb/gdb > (gdb) b main > (gdb) run I don't think that 676 is any worse than before, so I would not hold up 5.3 for this PR. I just tried your release criteria on Tru64 4.0f and 5.1a, and the test passed... My 2 cents... -- Joel