Alexandre Oliva writes: > 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.
Yeah, I discovered this today. Because your patch hadn't been flagged as affecting Java and no Java maintainer approved it, I hadn't noticed. > 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. Well, that was a bad thing to do. > 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? Please revert it, right now. It is impossible for anyone to debug gcj code at the moment. Once gdb support is in and widely distributed, then we can change gcc. Realistically, at least a year or two. Andrew. -- Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, UK Registered in England and Wales No. 3798903
