On Dec 19, 2007, Andrew Haley <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
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 [EMAIL PROTECTED], gcc.gnu.org}
Free Software Evangelist [EMAIL PROTECTED], gnu.org}
