Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Jim Ingham <jingham@apple.com>
Cc: gdb@sources.redhat.com
Subject: Re: [5.1/mi] Enable MI interface
Date: Wed, 21 Mar 2001 15:59:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010306104601.7922E-100000@is> (raw)
In-Reply-To: <200103052301.PAA00893@scv2.apple.com>

On Mon, 5 Mar 2001, Jim Ingham wrote:

> Should mean not too much.  If the ui_out stuff works on your host 
> platform, then you should pretty much get the MI for free.  It is 
> another command set for gdb, and a particular ui_out that formats the 
> output to these commands in a more deterministicly parseable way than 
> raw gdb console output.

IIRC MI is an interface between GDB and what/whoever is using GDB,
right?  If so, how, if at all, does it come into play in the normal
DJGPP usage where the user types command into GDB's CLI interface?
Does something convert these commands into MI before passing them to
GDB?

Or does the addition of MI simply mean that there's another command
language available to the user, which they can use as they see fit?
That is, unless the users actually type some MI commands, the MI code
will not spring into action at all?

Or am I missing the point entirely?


  reply	other threads:[~2001-03-21 15:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <983824932.9190.ezmlm@sources.redhat.com>
2001-03-21 15:59 ` gdb Digest 5 Mar 2001 20:42:12 -0000 Issue 473 Jim Ingham
2001-03-21 15:59 ` [5.1/mi] SYNTAX CHANGE? - List ``[ ]'' vs ``{ }'' Jim Ingham
2001-03-21 15:59   ` Fernando Nasser
2001-03-21 15:59 ` [5.1/mi] Enable MI interface Jim Ingham
2001-03-21 15:59   ` Eli Zaretskii [this message]
2001-03-21 15:59     ` Andrew Cagney
2001-03-21 15:59 Andrew Cagney
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59   ` Andrew Cagney
2001-03-21 15:59     ` Eli Zaretskii
2001-03-21 15:59       ` Andrew Cagney
2001-03-21 15:59         ` Eli Zaretskii

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=Pine.SUN.3.91.1010306104601.7922E-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=jingham@apple.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