From: Kip Macy <kmacy@eventdriven.org>
To: Brian McQueen <bmcqueen@tmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Gdb with Guile
Date: Thu, 30 Sep 2004 01:08:00 -0000 [thread overview]
Message-ID: <20040929180627.A91307@demos.bsdclusters.com> (raw)
In-Reply-To: <1096504520.17EBA60@g28.dngr.org>
With MI it is easy enough to interface with any language as well as
other applications such as GUIs. In-house I've got support for scripting
GDB with perl.
-Kip
On Wed, 29 Sep 2004, Brian McQueen wrote:
> I was wondering if you guys had considered linking guile in with gdb to
> provide the extension language functionality prior to going ahead with
> MI. With Guile it is very easy to add a lightweight, yet excellent
> extension language, and it is a complementary GNU project. I think it
> would be a fun project. That's why I'm asking - I'd like to do it
> myself. So I wonder if it was considered to be a bad idea. How did you
> arrive at MI1 and MI2? Being quite familiar with Guile, I think it
> would be a better choice.
>
> --bmcqueen
>
next prev parent reply other threads:[~2004-09-30 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 0:35 Brian McQueen
2004-09-30 1:08 ` Kip Macy [this message]
2004-10-02 15:38 ` Daniel Jacobowitz
2004-10-05 12:44 ` Andrew Cagney
2004-10-05 14:22 ` Brian McQueen
2004-10-06 1:46 ` Andrew Cagney
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=20040929180627.A91307@demos.bsdclusters.com \
--to=kmacy@eventdriven.org \
--cc=bmcqueen@tmail.com \
--cc=gdb@sources.redhat.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