This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: obvious set_cu_language patch
- To: Stan Shebs <shebs at apple dot com>
- Subject: Re: obvious set_cu_language patch
- From: Daniel Berlin <dan at www dot cgsoftware dot com>
- Date: Fri, 8 Jun 2001 17:33:57 -0400 (EDT)
- cc: Per Bothner <per at bothner dot com>, <gdb-patches at sources dot redhat dot com>
On Fri, 8 Jun 2001, Stan Shebs wrote:
> Per Bothner wrote:
> >
> > Daniel Berlin <dan@cgsoftware.com> writes:
> >
> > > dwarf2.h in gcc defines DW_LANG_Java as 0x000b.
> > > binutils/gdb's include/elf/dwarf2.h defines DW_LANG_Java as 0x9af4
> >
> > > Which is correct?
> >
> > I was going to say that I didn't know. But then I found:
> > http://reality.sgi.com/dehnert_engr/dwarf/d2-summary.html
> > Draft 6, page 139, lists:
> > DW_LANG_Java 0x000b
> >
> > I'll fix include/elf/dwarf2.h. I'm sure Stu Groassman just picked a
> > random number unlikely to conflict with some other assignment.
>
> When Stu did this, there was no mention of Java in the still-drafty
> Dwarf 2 spec. What's in GCC includes Dwarf 2.1 draft, so it's more
> recent, but beware of many inconsistencies. (diff of gcc/dwarf2.h
> and include/elf/dwarf2.h is positively scary, since they're supposed
> to be identical)
>
> Will GDB need to be able to recognize the old language code, perhaps
> in an old piece of gcj output?
Depends on how you look at it.
We couldn't before, obviously, and nobody complained, so ...
> You could leave the old code in
> dwarf2.h, just give it a different symbolic name.
>
> Stan
>