Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Lokesh Kumar" <lokeshk@gmail.com>
To: "Gordon Prieur" <Gordon.Prieur@sun.com>
Cc: gdb@sourceware.org
Subject: Re: GDB MI Interface
Date: Mon, 14 Apr 2008 02:18:00 -0000	[thread overview]
Message-ID: <baf3502a0804131441n11d449d2i1847720d954e7116@mail.gmail.com> (raw)
In-Reply-To: <47FF7ECA.4090104@sun.com>

Hi,

I think I found what I was looking for. Sharing it here for others as well.

On Fri, Apr 11, 2008 at 8:07 AM, Gordon Prieur <Gordon.Prieur@sun.com> wrote:
>
>  Lokesh Kumar wrote:
>
> > Hi all,
> >
> > I want to use the GDB MI interface to communicate with gdb in the
> > backend of my software. Surprisingly, the current information on this
> > topic is very less on the web. So I thought of turning to the gdb
> > community itself. I had the following questions to ask -
> >
> > 1. Does the parser for MI output already exists ?
> >
> >
>
>  No. You need to write your own.

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.
>
>
>
>
> > 2. Are there some frontends debugger that are using this ? As far as I
> > know, the ddd and kdb both use the CLI option.
> >
> >
>
>  The NetBeans C/C++ gdb module uses gdb/mi.
>
>
>
>
> > 3. Has there been any documentation on how to use gdb-MI. The current
> > documentation is, as they say, like a reference manual.
> >
> >
>
>  Chapter 25 of the gdb manual
> (http://sourceware.org/gdb/current/onlinedocs/gdb_25.html)
>  describes the interface.
>
>  Gordon
>
>
> > Thanks in advance,
> >
> > -Lokesh
> >
> >
> >
>



-- 
"Doubt is not a pleasant condition, but certainty is absurd."

Lokesh Kumar

Mobile: +1 917 319 0360


  reply	other threads:[~2008-04-13 21:41 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 [this message]
2008-04-14 13:32     ` Nick Roberts
2008-04-16  8:10       ` Doug Evans
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=baf3502a0804131441n11d449d2i1847720d954e7116@mail.gmail.com \
    --to=lokeshk@gmail.com \
    --cc=Gordon.Prieur@sun.com \
    --cc=gdb@sourceware.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