From: teawater <teawater@gmail.com>
To: drow@false.org, gdb@sourceware.org
Subject: Re: How about remote MI?
Date: Mon, 17 Jul 2006 13:26:00 -0000 [thread overview]
Message-ID: <daef60380607170619s7c7a57a1ib7d0c60cf39c87fb@mail.gmail.com> (raw)
In-Reply-To: <20060717005720.GA29042@nevyn.them.org>
Agree with you.
Thanks,
teawater
On 7/17/06, Daniel Jacobowitz <drow@false.org> wrote:
> On Sat, Jul 15, 2006 at 09:50:54PM +0800, teawater wrote:
> > Hi all,
> >
> >
> > 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?
>
> I do not see the point. GDB/MI talks to a terminal or a pipe. If you
> want to connect that pipe to a TCP socket, GDB doesn't need to know
> that it's a socket.
>
> You can use netcat to connect an arbitrary process to a bidirectional TCP
> socket. There's a bunch of other similar tools, too.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>
next prev parent reply other threads:[~2006-07-17 13:20 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
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 [this message]
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=daef60380607170619s7c7a57a1ib7d0c60cf39c87fb@mail.gmail.com \
--to=teawater@gmail.com \
--cc=drow@false.org \
--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