From: Alexandre Oliva <aoliva@redhat.com>
To: Andrew Haley <aph@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>, gcc@gcc.gnu.org
Subject: Re: Strange error message from gdb
Date: Thu, 20 Dec 2007 05:51:00 -0000 [thread overview]
Message-ID: <or1w9iq72u.fsf@oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <18281.27225.249982.220171@zebedee.pink> (Andrew Haley's message of "Wed\, 19 Dec 2007 19\:00\:41 +0000")
On Dec 19, 2007, Andrew Haley <aph@redhat.com> wrote:
> 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.
For very small values of "long while" :-)
This was added by:
2007-12-15 Alexandre Oliva <aoliva@redhat.com>
PR debug/7081
* lang.c (java_classify_record): New.
(LANG_HOOKS_CLASSIFY_RECORD): Override.
Sorry, I didn't check whether GDB or other debug information consumers
supported this tag. I just ASSumed they did, given how long they've
been specified (today Dwarf 3 turns 2 :-) and how noisy a failure
would be should one run into such a tag without supporting it.
What now, revert until GDB et al are fixed, or leave it in, for it's
the right thing to do, and it serves as an additional incentive for
debug information consumers to support new Dwarf 3 features?
Or introduce the -gdwarf-3 and get -gdwarf-2 (and -g?) to avoid using
Dwarf 3 features that are not backward compatible?
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2007-12-20 5:16 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
2007-12-19 19:05 ` Daniel Jacobowitz
2007-12-20 5:51 ` Alexandre Oliva [this message]
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=or1w9iq72u.fsf@oliva.athome.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=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).