From: Doug Evans <dje@google.com>
To: Nala Ginrut <mulei@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: About Guile support for GDB
Date: Sat, 15 Sep 2012 07:15:00 -0000 [thread overview]
Message-ID: <CADPb22RaSzsXD28MocxeMDNaaNKBQ3T93rx7-cRgKKu9RNbrJw@mail.gmail.com> (raw)
In-Reply-To: <20120915022738.GA14703@renee-laptop>
On Fri, Sep 14, 2012 at 7:27 PM, Nala Ginrut <mulei@gnu.org> wrote:
> hi! I saw the declaration on GDB website:
> -----------------------------cut----------------------------
> January 9, 2012: Extensibility support using Guile
> GDB ought to support extensibility using Guile,
> the GNU extensibility package (an implementation of Scheme).
> We are looking for people to write the code to interface the two.
> Please write to gdb-patches AT sourceware DOT org if you are interested.
> -----------------------------end----------------------------
>
> As a Guile developper, I'd like to contribute ;-)
> Would you please point me out how to start?
>
> Regards.
Here's an earlier thread on the subject.
http://sourceware.org/ml/gdb-patches/2012-06/msg00853.html
prev parent reply other threads:[~2012-09-15 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 2:27 Nala Ginrut
2012-09-15 7:15 ` Doug Evans [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=CADPb22RaSzsXD28MocxeMDNaaNKBQ3T93rx7-cRgKKu9RNbrJw@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=mulei@gnu.org \
/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