public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Gyula Gubacsi <gyula.gubacsi@gmail.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: Support of the D programming language
Date: Mon, 21 Nov 2011 21:06:00 -0000	[thread overview]
Message-ID: <m3sjlh6v9l.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAAL+MW9KH=cFVaBwvxva+R3qGHeh8G+=DcgNHWtOnvev_EVZHg@mail.gmail.com>	(Gyula Gubacsi's message of "Mon, 21 Nov 2011 14:27:52 +0000")

>>>>> "Gyula" == Gyula Gubacsi <gyula.gubacsi@gmail.com> writes:

Gyula> I've contacted with Mihail however he said that the support is failing
Gyula> due to some conflict with the DWARF4. (The 3 D-specific DWARF
Gyula> extensions are overlapping with some DWARF4 extensions
Gyula> http://d.puremagic.com/issues/show_bug.cgi?id=4180).
Gyula> As this should be resolved within the compiler development community,
Gyula> I would like to get comfortable to contribute to GDB the necessary D
Gyula> specific interface. I read the development resources however I still
Gyula> feel kinda lost in the GDB dev environment, I would appreciate if
Gyula> someone could help me out with some specific blog entries or similar,
Gyula> so I could catch up faster. (For first I would like to learn how to
Gyula> add reasonable test suites for testing the D interface.)

There's no easy way to learn a lot of this stuff.
You will end up having to read a lot of code.

I looked at the bug.  For DWARF extensions, I highly recommend
coordinating with GNU and putting the extension opcodes in the GNU part
of the vendor space.  Specifically I would recommend a page on the GCC
wiki describing the extension, plus a patch to include/dwarf2.h sent to
gcc-patches.  It is also friendly to also submit a proposal to DWARF
itself.

The DWARF reader in gdb is mostly in gdb/dwarf2read.c.  Your work would
probably be here, but may spill over to other places, depending on
exactly what support is needed to handle the various extensions.

For writing test cases, there is some documentation on dejagnu on the
web; and also some gdb-specific advice on the gdb wiki.  Since D support
is new, you would probably have to do more than is usual to get the
first test case written.

Tom

      reply	other threads:[~2011-11-21 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 16:31 Gyula Gubacsi
2011-11-08 16:41 ` Joel Brobecker
2011-11-21 14:28   ` Gyula Gubacsi
2011-11-21 21:06     ` Tom Tromey [this message]

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=m3sjlh6v9l.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=gyula.gubacsi@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).