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 19:05:00 -0000	[thread overview]
Message-ID: <18281.27225.249982.220171@zebedee.pink> (raw)
In-Reply-To: <20071219185517.GA10986@caradoc.them.org>

Daniel Jacobowitz writes:
 > On Wed, Dec 19, 2007 at 05:54:10PM +0000, Andrew Haley wrote:
 > >  > 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.
 > 
 > >From the DWARF standard:
 > 
 >  Interface types are represented by debugging information entries with
 >  the tag DW_TAG_interface_type.
 > 
 >  An interface type entry has a DW_AT_name attribute, whose value is a
 >  null-terminated string containing the type name as it appears in the
 >  source program.
 > 
 >  The members of an interface are represented by debugging information
 >  entries that are owned by the interface type entry and that appear in
 >  the same order as the corresponding declarations in the source
 >  program.

OK, so the name is missing, and that's wrong.  I should find out why.

 > So this is a declaration of an interface, but without a name.  GDB is
 > doing the wrong thing with it, but it still seems wrong to me.  Or do
 > Java interfaces have no name?
 > 
 > > 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.
 > 
 > That's just a complete transcription of the DWARF tags (at some point
 > in history).

Right, so read_type_die() doesn't know how to handle
DW_TAG_interface_type.  The weird thing is that I have never seen this
error mesage before today, and AFAIAA gcj has been generating these
interface types for a long while.

It seems to me that even if gcj did generate the name for the
interface, gdb would still die because it doesn't have any handlers
for DW_TAG_interface_type in dwarf2read.c

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 19:00 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
2007-12-19 19:00     ` Daniel Jacobowitz
2007-12-19 19:05       ` Andrew Haley [this message]
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.27225.249982.220171@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).