From: Doug Evans <dje@google.com>
To: Tom Emerson <tremerson@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB and Guile
Date: Thu, 28 Jun 2012 19:41:00 -0000 [thread overview]
Message-ID: <CADPb22Soewk-ZLJEY5y1NEBOLONzhC=YpTcFQCqO3ZuOnrqy4w@mail.gmail.com> (raw)
In-Reply-To: <CAOL6EhtNKDwKq3M56SLN_BpiyvE+1J4GvjS0E165cXSTMXk4yQ@mail.gmail.com>
On Thu, Jun 28, 2012 at 8:08 AM, Tom Emerson <tremerson@gmail.com> wrote:
> Greetings,
>
> I see on the GDB site that you were looking for people who might be
> interested in integrating GDB with Guile. I'm definitely interested in
> contributing to the project if there's room.
>
> Thanks for your time,
>
> -tree
Hi. There is indeed room.
The thing to do is to become familiar with libguile and with gdb's
Python interface, and come up with something sensible to provide in
gdb+guile what gdb provides today in gdb+python. Keeping the gdb side
of things (as opposed to the Python or Guile side of things) clean and
maintainable (given that we'd be now supporting multiple external
scripting languages) is of the utmost importance. [which isn't to say
the Python or Guile side are of lesser value of course :-)]
Have fun, and thanks!
next prev parent reply other threads:[~2012-06-28 19:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 15:09 Tom Emerson
2012-06-28 19:41 ` Doug Evans [this message]
2012-07-09 16:20 ` Ludovic Courtès
2012-07-09 20:35 ` Tom Emerson
2012-07-09 21:10 ` Tom Tromey
2012-07-10 13:30 ` Tom Emerson
[not found] <20120109032350.GJ2716@adacore.com>
2012-01-09 4:33 ` Andrey Smirnov
2012-01-09 16:24 ` Tom Tromey
[not found] ` <CA+jSXqa_SgOaNscr48FPiab5Tt+p2dJoD1A6B2Qbzbf3uXJs0g@mail.gmail.com>
2012-01-10 4:32 ` Joel Brobecker
2012-01-11 0:18 ` Jiang Jilin
2012-01-11 3:10 ` Mike Frysinger
2012-01-11 3:25 ` Joel Brobecker
2012-01-11 9:48 ` Mark Kettenis
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='CADPb22Soewk-ZLJEY5y1NEBOLONzhC=YpTcFQCqO3ZuOnrqy4w@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tremerson@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