From: Doug Evans <dje@sebabeach.org>
To: gdb-patches@sourceware.org, guile-user@gnu.org
Subject: guile scripting for gdb
Date: Mon, 04 Nov 2013 16:04:00 -0000 [thread overview]
Message-ID: <CAA8o+=QH-gHc2GoUadfhOO4hj0=mxRbC6u0CDijAsYRvWpzvyw@mail.gmail.com> (raw)
Hi.
fyi, I've uploaded my gdb-guile branch to github.
https://github.com/dje42/gdb.git
It's in branch gdb-guile.
It's still very preliminary, there's still lots to do, and there are
some open issues.
If you're interested take a look.
We'll have to see how things end up if/after it passes code review, so
while I welcome all the help I can get, I'd feel bad if people write
too much now only having to redo it.
OTOH, if you have as much fun with this stuff as I do, go for it. :-)
I'll be submitting snippets for review over the coming weeks.
next reply other threads:[~2013-11-04 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 16:04 Doug Evans [this message]
[not found] ` <87ob5vlr2s.fsf@gnu.org>
2013-11-09 19:47 ` Doug Evans
2013-11-09 19:48 ` Thien-Thi Nguyen
2013-11-10 6:26 ` Doug Evans
2013-11-11 1:50 ` Ludovic Courtès
2013-11-11 6:28 ` Doug Evans
2013-11-11 6:37 ` Doug Evans
2013-11-11 13:16 ` Ludovic Courtès
2013-11-11 11:55 ` Ludovic Courtès
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='CAA8o+=QH-gHc2GoUadfhOO4hj0=mxRbC6u0CDijAsYRvWpzvyw@mail.gmail.com' \
--to=dje@sebabeach.org \
--cc=gdb-patches@sourceware.org \
--cc=guile-user@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