From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13683 invoked by alias); 16 Mar 2004 16:00:13 -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 13649 invoked from network); 16 Mar 2004 16:00:09 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 16 Mar 2004 16:00:09 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1B3Gz7-0001vO-1A; Tue, 16 Mar 2004 11:00:05 -0500 Date: Tue, 16 Mar 2004 16:00:00 -0000 From: Daniel Jacobowitz To: Michael Elizabeth Chastain Cc: carlton@kealia.com, gdb@sources.redhat.com Subject: Re: gcc 3.4 regression in gdb.cp/namespace.exp Message-ID: <20040316160004.GA7287@nevyn.them.org> Mail-Followup-To: Michael Elizabeth Chastain , carlton@kealia.com, gdb@sources.redhat.com References: <20040316023921.33B114B104@berman.michael-chastain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040316023921.33B114B104@berman.michael-chastain.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-03/txt/msg00146.txt.bz2 On Mon, Mar 15, 2004 at 09:39:21PM -0500, Michael Chastain wrote: > David Carlton writes: > > ptype CClass::NestedClass > There is no field named NestedClass > (gdb) FAIL: gdb.cp/namespace.exp: ptype CClass::NestedClass > > This has been working fine for me with gdb HEAD, suite HEAD, gcc HEAD, > -gdwarf-2 since 2004-01-23. I got some FAILs on 2004-01-18 and > 2004-01-19. Have you run it since I committed the process_structure_scope patch on Saturday? I won't have time to really parse David's explanation for a couple of days but it sounds like I broke this. > > Do you really need gcc 3.5.0 20040119? > Can you try gcc 3.5.0 20040315 for example? > > > I really hate the way we test our DWARF 2 reader - there's no way to > > generate the debug info by hand to give a particular scenario, so > > instead we have to hope that we can find the magic version of GCC and > > magic way of writing a test case to trigger the bug in question. > > Sigh. > > Can we write a gdb.dwarf-2 that looks like gdb.stabs, > with assembly language input in it? > > Michael C > -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer