From: Nick Roberts <nickrob@snap.net.nz>
To: teawater <teawater@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: How about remote MI?
Date: Sat, 15 Jul 2006 15:13:00 -0000 [thread overview]
Message-ID: <17593.486.472132.416318@kahikatea.snap.net.nz> (raw)
In-Reply-To: <daef60380607150650o3525235rb6526def836bd5ce@mail.gmail.com>
> 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
> 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.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-07-15 14:57 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 [this message]
2006-07-15 17:27 ` teawater
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=17593.486.472132.416318@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sourceware.org \
--cc=teawater@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