From: Daniel Jacobowitz <drow@false.org>
To: Bob Rossi <bob_rossi@cox.net>
Cc: teawater <teawater@gmail.com>, gdb@sourceware.org
Subject: Re: How about remote MI?
Date: Mon, 17 Jul 2006 13:49:00 -0000 [thread overview]
Message-ID: <20060717134320.GA10281@nevyn.them.org> (raw)
In-Reply-To: <20060717132709.GB513@brasko.net>
On Mon, Jul 17, 2006 at 09:27:10AM -0400, Bob Rossi wrote:
> There ia at least one possibility I can think of that would improve
> upon GDB/MI by having it connect back to the FE via a TCP socket.
>
> That is, it would avoid the 'tty' issue, by allowing the FE to put a
> single pty between the FE and GDB, and having all the MI protocol
> on a totally separate channel.
I don't see any advantage over using the "set tty" command now that
we've got it...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-17 13:43 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
2006-07-17 13:43 ` Bob Rossi
2006-07-17 13:49 ` Daniel Jacobowitz [this message]
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=20060717134320.GA10281@nevyn.them.org \
--to=drow@false.org \
--cc=bob_rossi@cox.net \
--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