From: Daniel Jacobowitz <drow@false.org>
To: John Demme <me@teqdruid.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: D Symbol Demangling
Date: Fri, 08 Apr 2005 21:11:00 -0000 [thread overview]
Message-ID: <20050408211129.GA16851@nevyn.them.org> (raw)
In-Reply-To: <1112993463.32374.81.camel@localhost.localdomain>
On Fri, Apr 08, 2005 at 04:51:03PM -0400, John Demme wrote:
> On Fri, 2005-04-08 at 12:52 -0400, Daniel Jacobowitz wrote:
> > On Fri, Apr 08, 2005 at 12:47:51PM -0400, John Demme wrote:
> > > I finally had time to play firefighter, and I found the fire as well.
> > > If you compile a D application without DWARF2 information, my gdb
> > > patches work just fine... how do ya like that?
> > >
> > > Now I REALLY have an excuse to yell at the compiler programmer.
> > >
> > > I don't really understand why bad DWARF2 information would screw up GDB
> > > like that, considering that I call my function at the point where GDB
> > > tries to demangle a symbol, but I don't really understand how GDB works.
> > >
> > > Thanks for your help... Expect to hear more from me in the future
> > > concerning this.
> >
> > Presumably because you don't have a DWARF language code for D. What's
> > it labelling the language as in the DW_TAG_compile_unit DIE?
> >
>
> According to the compiler programmer,
> "The DW_TAG_compile_unit is not the right thing. What it does do is
> write
> into the prolog DW_LANG_C89, masquerading as C. When GDB gets a
> DW_LANG_D,
> I'll switch to that."
>
> I assume this is correct... so does anyone know what is involved in
> getting DW_LANG_D? Where might one find contact information for the
> DWARF working group?
See: http://dwarf.freestandards.org/
> There are currently two. DMD, the reference implementation, has an open
> source front-end, and a closed-source backend. GDC, the other compiler,
> uses the front-end from DMD, and GCC's backend. I'm not sure what this
> means for operation with GDB. It would be nice to have possible
> inconsistencies in the D language spec, so as to avoid them. Since I'm
> currently working on it, I'm going to suggest the DMD's method of symbol
> mangling become part of the spec. Keeping in mind that D is very
> similar to C, is there anything else I should suggest?
I have no idea.
> > If you want to do this, you will eventually need a GDB copyright
> > assignment with the FSF.
> >
> I assume this is to assign copyrights to the FSF... I have no problem
> with that. Where do I sign up?
I'll send it to you.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-04-08 21:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 2:37 John Demme
2005-04-04 18:21 ` Michael Snyder
2005-04-04 20:44 ` John Demme
2005-04-04 20:47 ` Daniel Jacobowitz
2005-04-04 21:49 ` Michael Snyder
2005-04-04 22:39 ` John Demme
[not found] ` <1112654359.14153.50.camel@localhost.localdomain>
[not found] ` <4251CF00.5080002@redhat.com>
2005-04-08 16:47 ` John Demme
2005-04-08 16:52 ` Daniel Jacobowitz
2005-04-08 20:50 ` John Demme
2005-04-08 21:11 ` Daniel Jacobowitz [this message]
2006-04-19 11:18 Thomas Kuehne
2006-04-20 13:20 ` Daniel Jacobowitz
2006-04-21 21:25 ` Thomas Kühne
2006-04-22 22:52 ` Thomas Kühne
2006-04-24 17:21 ` Jim Blandy
2006-04-24 20:53 ` Daniel Jacobowitz
2006-04-25 3:35 ` Eli Zaretskii
2006-04-25 14:13 ` DJ Delorie
2006-04-29 7:23 ` Thomas Kühne
2006-04-29 16:47 ` DJ Delorie
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=20050408211129.GA16851@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=me@teqdruid.com \
/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