From: Tom Emerson <tremerson@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB and Guile
Date: Mon, 09 Jul 2012 20:35:00 -0000 [thread overview]
Message-ID: <CAOL6EhuRQ8OqkOvKRVwXpfhG=5kzEDDrOD-Yzk1pChS7c8WVHA@mail.gmail.com> (raw)
In-Reply-To: <87y5msdhzz.fsf@gnu.org>
On Mon, Jul 9, 2012 at 12:19 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> Please don’t hesitate to ask for feedback on guile-user@gnu.org, or on
> #guile on Freenode. We’d be happy to support you in this endeavor. :-)
Thanks Ludo. At this point I've been reading through the current
Python integration in GDB to get a feel for where the common touch
points would be. I'm also looking at the various Python examples and
re-imagining them in Scheme. What, if anything, has been done related
to Guile/GDB integration heretofore? Has anyone collected a wish list
or something similar? Parity with the Python functionality is
obviously the first order of business, which in turn speaks to
generalizing the interface between GDB and Python so that it is more
(extension language) neutral.
Peace,
-tree
--
Tom Emerson
tremerson@gmail.com
http://www.dreamersrealm.net/tree
next prev parent reply other threads:[~2012-07-09 20:35 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
2012-07-09 16:20 ` Ludovic Courtès
2012-07-09 20:35 ` Tom Emerson [this message]
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='CAOL6EhuRQ8OqkOvKRVwXpfhG=5kzEDDrOD-Yzk1pChS7c8WVHA@mail.gmail.com' \
--to=tremerson@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=ludo@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