From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6448 invoked by alias); 16 Mar 2004 16:37:32 -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 6367 invoked from network); 16 Mar 2004 16:37:26 -0000 Received: from unknown (HELO hawaii.kealia.com) (209.3.10.89) by sources.redhat.com with SMTP; 16 Mar 2004 16:37:26 -0000 Received: by hawaii.kealia.com (Postfix, from userid 2049) id 89880C60E; Tue, 16 Mar 2004 08:37:23 -0800 (PST) To: mec.gnu@mindspring.com (Michael Elizabeth Chastain) Cc: gdb@sources.redhat.com, drow@mvista.com Subject: Re: gcc 3.4 regression in gdb.cp/namespace.exp References: <20040316023921.33B114B104@berman.michael-chastain.com> From: David Carlton Date: Tue, 16 Mar 2004 16:37:00 -0000 In-Reply-To: <20040316023921.33B114B104@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Mon, 15 Mar 2004 21:39:21 -0500 (EST)") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Reasonable Discussion, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-03/txt/msg00148.txt.bz2 On Mon, 15 Mar 2004 21:39:21 -0500 (EST), mec.gnu@mindspring.com (Michael Elizabeth Chastain) said: > 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. Hmm. Well, I'm checking out gcc-3_4-branch as we speak, so we'll see how it goes. (And at some point I'll update my mainline GCC, too.) As Daniel says, this may be a very recent bug in GDB, so you may not have seen it. (Or it may be that the GCC I'm using is generating valid DWARF-2 which happens to be different from the current GCC snapshot, for that matter.) >> 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? That's a good idea; I'll think about that. David Carlton carlton@kealia.com