From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
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: <3AA417E8.4F9A1348@cygnus.com> (raw)
In-Reply-To: <200103052020.PAA15012@indy.delorie.com>
Eli Zaretskii wrote:
>
> > Date: Sun, 04 Mar 2001 21:29:44 -0500
> > From: Andrew Cagney <ac131313@cygnus.com>
> >
> > A 5.1 release criteria is enabling the MI interface.
> >
> > Once my other MI questions get resolved, the biggest problem I can see
> > with this is with the MI testsuite. Once MI is enabled the testsuite
> > will kick in and, most likely, some targets will have additional
> > failures.
> >
> > If anyone can see any problems with this, please start rasing them now
> > :-) The change required to enable the MI is trivial. The consequences
> > may not be :-)
>
> Bother. Can you, or someone else, please describe in a few words what
> does "enable the MI interface" mean, in practical terms, for a port
> such as the DJGPP port?
Nothing (yes, ok famous last words :-).
At present the gdb/mi directory isn't built. Enabling the MI would mean
building that directory and linking it into GDB. For a DJGPP user, this
just means that GDB gained a few kilos.
The big change really occured ~2 months ago when ui-out became the
normal mechanism to use when outputing something. Since the old
*_printf() interface remains, no one noticed (1) :-)
enjoy,
Andrew
(1) Almost no one. There were a few bugs where the output changed
slightly and where found the output was fixed.
next prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 15:59 Andrew Cagney
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Andrew Cagney [this message]
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Eli Zaretskii
[not found] <983824932.9190.ezmlm@sources.redhat.com>
2001-03-21 15:59 ` Jim Ingham
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Andrew Cagney
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=3AA417E8.4F9A1348@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--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