Re: Strange error message from gdb

2007-12-22 Thread Jan Kratochvil
On Thu, 20 Dec 2007 15:33:14 +0100, Andrew Haley wrote: > Alexandre Oliva writes: > > > > How about this patch, instead? It will restore debuggability to Java > > while at the same time maintaining the progress of using the > > long-supported-by-GDB DW_TAG_class_type in both C++ and Java. > > >

Re: Strange error message from gdb

2007-12-20 Thread Andrew Haley
Alexandre Oliva writes: > > How about this patch, instead? It will restore debuggability to Java > while at the same time maintaining the progress of using the > long-supported-by-GDB DW_TAG_class_type in both C++ and Java. > > for gcc/java/ChangeLog > from Alexandre Oliva <[EMAIL PROT

Re: Strange error message from gdb

2007-12-20 Thread Alexandre Oliva
On Dec 20, 2007, Andrew Haley <[EMAIL PROTECTED]> wrote: > Alexandre Oliva writes: >> 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 maintain

Re: Strange error message from gdb

2007-12-20 Thread Andrew Haley
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

Re: Strange error message from gdb

2007-12-19 Thread Alexandre Oliva
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 ve

Re: Strange error message from gdb

2007-12-19 Thread Daniel Jacobowitz
On Wed, Dec 19, 2007 at 07:00:41PM +, Andrew Haley wrote: > 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 Yes, you're probably right. It thinks it's some kind of s

Re: Strange error message from gdb

2007-12-19 Thread Andrew Haley
Daniel Jacobowitz writes: > On Wed, Dec 19, 2007 at 05:54:10PM +, 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 inte

Re: Strange error message from gdb

2007-12-19 Thread Daniel Jacobowitz
On Wed, Dec 19, 2007 at 05:54:10PM +, 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. >F

Re: Strange error message from gdb

2007-12-19 Thread Andrew Haley
Daniel Jacobowitz writes: > On Wed, Dec 19, 2007 at 05:21:50PM +, 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 d

Re: Strange error message from gdb

2007-12-19 Thread Daniel Jacobowitz
On Wed, Dec 19, 2007 at 05:21:50PM +, 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] > >

Strange error message from gdb

2007-12-19 Thread Andrew Haley
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