From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9417 invoked by alias); 15 Nov 2010 20:29:33 -0000 Received: (qmail 9409 invoked by uid 22791); 15 Nov 2010 20:29:32 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from seketeli.net (HELO ms.seketeli.net) (91.121.166.71) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 15 Nov 2010 20:28:50 +0000 Received: from adjoa.torimasen.com (torimasen.com [82.237.12.13]) by ms.seketeli.net (Postfix) with ESMTP id 1668E1608038; Mon, 15 Nov 2010 21:21:40 +0100 (CET) Received: from adjoa.seketeli.org (localhost.localdomain [127.0.0.1]) by adjoa.torimasen.com (Postfix) with ESMTP id 4346B8E601B; Mon, 15 Nov 2010 21:28:46 +0100 (CET) From: Dodji Seketeli To: Michel METZGER Cc: Tom Tromey , "gdb\@sourceware.org" Subject: Re: Bad struct name in gdb with g++ 4.1.2 References: <5B4CE209869C6A4797F5FAA0B348F0A0D9EA8C20A7@SAFEX1MAIL1.st.com> <5B4CE209869C6A4797F5FAA0B348F0A0D9EA8C20EB@SAFEX1MAIL1.st.com> X-URL: http://www.seketeli.net/~dodji Date: Mon, 15 Nov 2010 20:29:00 -0000 In-Reply-To: <5B4CE209869C6A4797F5FAA0B348F0A0D9EA8C20EB@SAFEX1MAIL1.st.com> (Michel METZGER's message of "Tue, 2 Nov 2010 20:52:55 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-11/txt/msg00065.txt.bz2 Michel METZGER a =C3=A9crit: > readelf -wi gives me the following=20 > > [...] > <1><66>: Abbrev Number: 2 (DW_TAG_structure_type) > DW_AT_sibling : <8e> > DW_AT_name : ._0 > DW_AT_byte_size : 8 > DW_AT_decl_file : 3 > DW_AT_decl_line : 1 > [...] > > This is a compiler bug then. Could you please check if you still have the problem with GCC 4.4 or 4.5? If yes, please file a bug to http://gcc.gnu.org/bugzilla with your testcase. At least the information will not get lost. Who knows, someone could even fix the problem ;-) --=20 Dodji