public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Strange error message from gdb
Date: Wed, 19 Dec 2007 18:01:00 -0000	[thread overview]
Message-ID: <18281.23234.151870.816362@zebedee.pink> (raw)
In-Reply-To: <20071219172943.GA5939@caradoc.them.org>

Daniel Jacobowitz writes:
 > On Wed, Dec 19, 2007 at 05:21:50PM +0000, Andrew Haley wrote:
 > > Die: DW_TAG_interface_type (abbrev = 23, offset = 4181)
 > > 	has children: FALSE
 > > 	attributes:
 > > 		DW_AT_declaration (DW_FORM_flag) flag: TRUE
 > > Dwarf Error: Cannot find type of die [in module /home/aph/a.out]
 > > 
 > > I suppose this means that gcj is generating bad debug info, but I
 > > don't know what it's complaining about exactly, so I don't know how to
 > > fix it.
 > > 
 > > Here's the abbrev in question:
 > > 
 > >  <1><1055>: Abbrev Number: 23 (DW_TAG_interface_type)
 > >   <1056>     DW_AT_declaration : 1      
 > 
 > That DIE doesn't have any content.  It says "I am a declartion of an
 > interface".  But not which interface or what it's called or what the
 > type is.

Well, the type is the interface: there's nothing else it might be.

 > I'd need a backtrace to be more specific, but in addition to bad
 > debug info this may be a limitation in GDB; it does not know
 > anything about DW_TAG_interface_type.

OK, thanks.

Anyway, on inspection it seems like read_type_die() in dwarf2read.c
doesn't know how to handle DW_TAG_interface_type.  This is rather odd,
given that dwarf_tag_name() does know about interface types.

Maybe I should just fix gcj not to use DW_TAG_interface_type.

Andrew.

-- 
Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, UK
Registered in England and Wales No. 3798903

  reply	other threads:[~2007-12-19 17:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 17:29 Andrew Haley
2007-12-19 17:54 ` Daniel Jacobowitz
2007-12-19 18:01   ` Andrew Haley [this message]
2007-12-19 19:00     ` Daniel Jacobowitz
2007-12-19 19:05       ` Andrew Haley
2007-12-19 19:05         ` Daniel Jacobowitz
2007-12-20  5:51         ` Alexandre Oliva
2007-12-20 14:24           ` Andrew Haley
2007-12-20 14:33             ` Alexandre Oliva
2007-12-20 15:09               ` Andrew Haley
2007-12-22 22:49                 ` Jan Kratochvil

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=18281.23234.151870.816362@zebedee.pink \
    --to=aph@redhat.com \
    --cc=drow@false.org \
    --cc=gcc@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).