Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michel METZGER <michel.metzger@st.com>
To: Tom Tromey <tromey@redhat.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Bad struct name in gdb with g++ 4.1.2
Date: Tue, 02 Nov 2010 19:53:00 -0000	[thread overview]
Message-ID: <5B4CE209869C6A4797F5FAA0B348F0A0D9EA8C20EB@SAFEX1MAIL1.st.com> (raw)
In-Reply-To: <m3wrov5x9k.fsf@fleche.redhat.com>

readelf -wi gives me the following 

[...]
<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.

Thanks,

Michel

-----Original Message-----
From: Tom Tromey [mailto:tromey@redhat.com] 
Sent: Tuesday, November 02, 2010 3:41 PM
To: Michel METZGER
Cc: gdb@sourceware.org
Subject: Re: Bad struct name in gdb with g++ 4.1.2

>>>>> "Michel" == Michel METZGER <michel.metzger@st.com> writes:

Michel> I'm having some issues with debugging an application compiled
Michel> with g++ 4.1.2 The type names for structures appear in gdb as
Michel> ".0", ".1", etc.

[...]

Michel> A more recent version of gdb (7.1) gives the same results.
Michel> A more recent version of gcc (4.5.1) gives the expected results.

Michel> Any idea?

I would suggest looking at the debuginfo.
You can do this with "readelf -wi".
If that shows the strange names, then it is a compiler bug.

Tom


  reply	other threads:[~2010-11-02 19:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 18:43 Michel METZGER
2010-11-02 19:37 ` Tom Tromey
2010-11-02 19:53   ` Michel METZGER [this message]
2010-11-15 20:29     ` Dodji Seketeli
2010-11-15 20:45       ` Michel METZGER

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5B4CE209869C6A4797F5FAA0B348F0A0D9EA8C20EB@SAFEX1MAIL1.st.com \
    --to=michel.metzger@st.com \
    --cc=gdb@sourceware.org \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox