Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Thomas Elam <tomelam@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: What are the prescribed ways to extend gdb? Examples?
Date: Tue, 08 Feb 2005 16:46:00 -0000	[thread overview]
Message-ID: <4208EBBD.30307@gnu.org> (raw)
In-Reply-To: <6251c71605010208593729d960@mail.gmail.com>

Thomas Elam wrote:

Just FYI, your e-mail answers your own question -> the assumptions and 
expectations are all correct.  MI has clear traction amongst the various 
IDE developers (EMACS, Eclipse's CDT).

Andrew


> What are the currently prescribed ways to extend
> gdb?  I am interested in adding to gdb: (1) a full
> scripting language (not tcl) or (2) a new GUI front-end.
> These additions could use the same or different
> methods of extending gdb.  I *might* want to link my
> code in with gdb.  I much prefer a machine-oriented
> interface to a human-oriented one.
> 
> I have found the following references about extending gdb:
> 
> [1] Section 4.2 of the `GDB Internals' document,
> `UI-Independent Output--the ui_out Function':
> http://sources.redhat.com/gdb/current/onlinedocs/gdbint_4.html#SEC19
> 
> [2] Section 24 of the `Debugging with GDB'
> document, `The GDB/MI Interface':
> http://sources.redhat.com/gdb/current/onlinedocs/gdb_25.html#SEC223
> This is also described in the part of GDB's info page
> related to the `-interface' option.
> 
> [3] Section A of the `GDB Internals' document, `GDB
> Currently available observers':
> http://sources.redhat.com/gdb/current/onlinedocs/gdbint_19.html#SEC188
> 
> It looks like [2] is the way to go for people
> who are not maintainers of gdb.
> 
> Examples?  I've found Insight, but I think it links
> into gdb and is apparently hard to maintain for that
> reason.  As far as I know, most or all of the front-
> ends to gdb open gdb as a separate process and
> parse its human-oriented output, which is not
> ideal, with the exception of an interface written by
> Moses Dejong.  He describes his scripting interface
> to gdb in this paper:
> http://www.tcl.tk/community/tcl2004/Tcl2003papers/dejong.pdf
> Near the end of the paper, he tells where the
> Tcl source code for the interface can be found:
> http://www.uncounted.org/tcl/gdbmi-0.1.tgz
> It uses version 1 of GDB's MI (machine-oriented)
> interface.  I've tried this Tcl interface with
> the Debian package gdb-6.3-5 .  It seems to work,
> but I have to work with it some more, since I don't
> remember much Tcl.
> 
> Any advice for me?
> 


      parent reply	other threads:[~2005-02-08 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-02 16:59 Thomas Elam
2005-01-02 17:06 ` Thomas Elam
2005-01-02 17:12   ` Thomas Elam
2005-02-08 16:46 ` Andrew Cagney [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=4208EBBD.30307@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=tomelam@gmail.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