Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob_rossi@cox.net>
To: gdb@sources.redhat.com
Subject: Re: GDB/MI & CLI commands
Date: Sat, 08 Feb 2003 02:58:00 -0000	[thread overview]
Message-ID: <20030208025807.GA8872@white> (raw)
In-Reply-To: <1044650036.1857.15.camel@lindt.uglyboxes.com>

On Fri, Feb 07, 2003 at 12:33:56PM -0800, Keith Seitz wrote:
> On Fri, 2003-02-07 at 07:10, Bob Rossi wrote:
> > However, I would like to confirm that GDB/MI is supposed to
> > accept CLI commands.
> 
> It does for now, but this behavior is only temporary. It was used as a
> stop-gap for commands that are not yet implemented (from mi-main.c):
> 
>     case CLI_COMMAND:
>       /* A CLI command was read from the input stream */
>       /* This will be removed as soon as we have a complete set of
>          mi commands */
> 
> Note that CLI commands read in via MI (not via -interpreter-exec) will
> have MI output semantics.
> 
> Keith
> 

Keith, 
Please excuse my ignorance.

When GDB is started like this './gdb --interpreter=mi <program>',
the mi interface is given. 

I understand that the client can then communicate with gdb by 
issuing mi commands and getting back mi responses.

I would like to know if in the official release of mi ( when its basically
complete ) will accept CLI commands from the client and give back mi
responses?

This is important to me since I plan on implementing a console for the
user to issue CLI commands.

What is the difference between MI and -interpreter-exec?

Thanks for your patience,
Bobby


  reply	other threads:[~2003-02-08  2:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07 14:55 Bob Rossi
2003-02-07 15:10 ` Bob Rossi
2003-02-07 20:29   ` Keith Seitz
2003-02-08  2:58     ` Bob Rossi [this message]
2003-02-08 15:55       ` Keith Seitz

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=20030208025807.GA8872@white \
    --to=bob_rossi@cox.net \
    --cc=gdb@sources.redhat.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