From: "André Pönitz" <apoenitz@trolltech.com>
To: gdb@sourceware.org
Subject: Re: GDB MI Interface
Date: Fri, 11 Apr 2008 12:19:00 -0000 [thread overview]
Message-ID: <200804110955.38021.apoenitz@trolltech.com> (raw)
In-Reply-To: <baf3502a0804101707ja4dcbefo7ca6a0f9388e19dc@mail.gmail.com>
On Friday 11 April 2008 02:07:15 Lokesh Kumar wrote:
> Hi all,
Hi Lokesh.
> 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 ?
I am not aware of an "official" MI parser. I am using a home grown one
which is ~260 lines of straight-forward C++, It's probably not complete,
but reads the parts I am interested in sufficiently well ;-)
> 2. Are there some frontends debugger that are using this ? As far as I
> know, the ddd and kdb both use the CLI option.
See Vladimir's posting ;-)
Apart from that I am trying to use MI as it relays structured data much better
then the CLI. The two main problems with gdb/MI is that it is (a) incomplete,
so there are lots of "traditional" commands that do not have an MI equivalent
or whose MI equivalent just chickens out saying "not implemented", and
(b) that it seems to be a constant flux.
It's a bit of a trade-off. _Not_ using MI would give an imaginary frontend
the possibility to use Intel's debugger, too, as this can be configured
to look pretty much like the gdb CLI.
> 3. Has there been any documentation on how to use gdb-MI. The current
> documentation is, as they say, like a reference manual.
Chapter 24 in the docs found on
http://sourceware.org/gdb/current/onlinedocs/gdb_toc.html
is usable. The problem is that there are different flavours of MI out in
the wild, and point (b) above leading to the necessity to double-check
anything written in the docs with the actual gdb incarnations you want to
support - which is a wee bit less convienient than you could dream of
in a perfect world ;-)
Regards,
Andre'
next prev parent reply other threads:[~2008-04-11 7:55 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 [this message]
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
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=200804110955.38021.apoenitz@trolltech.com \
--to=apoenitz@trolltech.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