Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: "Nick Roberts" <nickrob@snap.net.nz>
Cc: gdb@sourceware.org
Subject: Re: How about remote MI?
Date: Sun, 16 Jul 2006 06:56:00 -0000	[thread overview]
Message-ID: <daef60380607152342j39e5c83i229a26ea228d91a2@mail.gmail.com> (raw)
In-Reply-To: <17593.49525.303202.339890@kahikatea.snap.net.nz>

GDBRUI(http://sourceforge.net/projects/gdbrui/) is not like TUI. I
think It like MI. MI support a PIPE interface. GDBRUI support a TCP/IP
interface to other program. So the program that is in another machine
can control GDB via TCP/IP.
So I think maybe I can do some work to make MI support TCP/IP
interface. How do you think about it?

On 7/16/06, Nick Roberts <nickrob@snap.net.nz> wrote:
>  > > 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
>
> TUI is an interpreter too, but it's not a machine interface like MI.  I think
> you have said that with GDBRUI the user still interacts with the command line
> which makes it sound more like TUI.  You may have done something brilliant and
> single handedly written an interface that is better than MI, but you don't
> currently have mind share.  I think if we are to follow what you have done,
> and what you want to achieve, you have to take things in smaller steps.  What
> advantages does GDBRUI have over MI?  One or two simple examples would be good
> to start with.
>
>
> --
> Nick                                           http://www.inet.net.nz/~nickrob
>


  reply	other threads:[~2006-07-16  6:42 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 [this message]
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=daef60380607152342j39e5c83i229a26ea228d91a2@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