From: teawater <teawater@gmail.com>
To: "Nick Roberts" <nickrob@snap.net.nz>
Cc: gdb@sourceware.org
Subject: Re: How about remote MI?
Date: Sat, 15 Jul 2006 17:27:00 -0000 [thread overview]
Message-ID: <daef60380607150813u60080a60g8a12a3f06a61c6f7@mail.gmail.com> (raw)
In-Reply-To: <17593.486.472132.416318@kahikatea.snap.net.nz>
On 7/15/06, Nick Roberts <nickrob@snap.net.nz> wrote:
> > In May, I release GDBRUI(http://sourceforge.net/projects/gdbrui/) that
> > is an interpreter to make GDB can be controlled by the other programe
> > through TCP. But some people ask me why not extend MI to support TCP.
> > Now, I think this idea is cool. Does GDB MI support TCP? Maybe I can
> > extend MI to support TCP. How do you think about it?
>
> gdbserver supports TCP. You can control a remote program using MI and
> gdbserver. MI is a formal interface for use by front ends. I'm not sure that
> gdbrui, as you describe it, fills the same role
>
MI is an interpreter.
GDBRUI is an interpreter too.
interps.c
> > BTW, I am trying to make vim2gdb (An vim plug-in to make vim can debug
> > code through GDB. It use GDBRUI in before.) support MI. But the MI
> > output format is not very easy to parse. Could some people recommend a
> > programe or example that parse the MI output for me? If not, I think I
> > will use lex to parse it.
>
> I think the idea is that the front end parses it directly. Generating an
> intermediate langusage just adds to the complexity. If you think MI can
> be improved then please make suggestions.
My means is that I need parse MI output in other programe.
>
>
> --
> Nick http://www.inet.net.nz/~nickrob
>
next prev parent reply other threads:[~2006-07-15 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 14:57 teawater
2006-07-15 15:13 ` Nick Roberts
2006-07-15 17:27 ` teawater [this message]
2006-07-16 6:42 ` Nick Roberts
2006-07-16 6:56 ` teawater
2006-07-16 12:02 ` Nick Roberts
2006-07-16 14:08 ` Bob Rossi
2006-07-17 0:59 ` Daniel Jacobowitz
2006-07-17 13:26 ` teawater
2006-07-17 13:43 ` Bob Rossi
2006-07-17 13:49 ` Daniel Jacobowitz
2006-07-17 19:28 ` 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=daef60380607150813u60080a60g8a12a3f06a61c6f7@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb@sourceware.org \
--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