public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Brian McQueen <bmcqueen@tmail.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sources.redhat.com
Subject: Re: Gdb with Guile
Date: Tue, 05 Oct 2004 12:44:00 -0000	[thread overview]
Message-ID: <4161B0A5.5020502@gnu.org> (raw)
In-Reply-To: <20041002151402.GA24203@nevyn.them.org>

> On Wed, Sep 29, 2004 at 05:32:48PM -0700, 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.
> 
> 
> MI solves a different problem than Guile would.  MI is not an extension
> language; it is a mechanism to interact with GDB in a machine-parseable
> fashion from an external program.

Actually it does, and when MI was being architected, possibilities such 
as GUILE were very much on the mind of the designer [i.e., me :-)]

GDB is trying to head in the direction of having MI (and CLI) to be 
implemented as thin vineers over a libgdb object and set of primatives. 
  Scripting languages, such as GUILE, would either use the MI interface 
(as gdb/mi/gdb-mi.el does), or the primatives just below.  Pieces are 
slowly falling into place - observers, ui-out builder - but others such 
as async targets are still a problem.

Just beware of the now very defunct libgdb v1 that was removed some time 
ago.  The old paper http://www.gnu.org/software/gdb/papers/libgdb2/ also 
contains additional background.

We've just a small matter of programming :-^.

Andrew



  reply	other threads:[~2004-10-05 12:34 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
2004-10-02 15:38 ` Daniel Jacobowitz
2004-10-05 12:44   ` Andrew Cagney [this message]
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=4161B0A5.5020502@gnu.org \
    --to=cagney@gnu.org \
    --cc=bmcqueen@tmail.com \
    --cc=drow@false.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).