Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Doug Evans" <dje@google.com>
To: "Nick Roberts" <nickrob@snap.net.nz>
Cc: "Lokesh Kumar" <lokeshk@gmail.com>,
	        "Gordon Prieur" <Gordon.Prieur@sun.com>,
	gdb@sourceware.org
Subject: Re: GDB MI Interface
Date: Wed, 16 Apr 2008 08:10:00 -0000	[thread overview]
Message-ID: <e394668d0804151346o28740f08h162a5dcbc8e37b55@mail.gmail.com> (raw)
In-Reply-To: <18434.33686.377360.769555@kahikatea.snap.net.nz>

On Sun, Apr 13, 2008 at 3:05 PM, Nick Roberts <nickrob@snap.net.nz> wrote:
>  > http://sourceforge.net/projects/libmigdb/
>   >
>   > This library provides all the function that one may need to start gdb,
>   > interact with it (seeting breakpoints, watchpoints, run, stop, step
>   > etc.) and parse the output. A good tool for someone planning to use
>   > GDB MI.
>
>  It appears that the last release was 2004-07-20 and that there is no mailing
>  list.  I don't recall the author being active on this list.  MI is still
>  evolving so I suggest that if you are are going to use this library that you
>  follow events here and share your experiences.

I wonder if it would be useful to add something like this to the GDB
tree.  Maybe not this specific implementation, but something with the
same purpose.  Put a python wrapper on it and ... cool.  OTOH, it'd be
sort of like the new python scripting support but inverted (python
<--> gdb instead of gdb <--> python, if that makes any sense).

Is it lamentable that we have both gdbmi and (soon) a real scripting
interface with no real commonality?  Just thinking out loud ... I
don't have an answer.


  reply	other threads:[~2008-04-15 20:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11  7:55 Lokesh Kumar
2008-04-11 10:52 ` Vladimir Prus
2008-04-11 14:31   ` Marc Khouzam
2008-04-11 12:19 ` André Pönitz
2008-04-12 22:46 ` Gordon Prieur
2008-04-14  2:18   ` Lokesh Kumar
2008-04-14 13:32     ` Nick Roberts
2008-04-16  8:10       ` Doug Evans [this message]
2008-04-16  9:47         ` Tom Tromey
2008-04-16 15:20         ` Daniel Jacobowitz
2008-04-14 13:43     ` Bob Rossi

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=e394668d0804151346o28740f08h162a5dcbc8e37b55@mail.gmail.com \
    --to=dje@google.com \
    --cc=Gordon.Prieur@sun.com \
    --cc=gdb@sourceware.org \
    --cc=lokeshk@gmail.com \
    --cc=nickrob@snap.net.nz \
    /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