From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Discussion <gdb@sources.redhat.com>
Subject: [5.1/mi] Enable MI interface
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <3AA2FA18.79205BFE@cygnus.com> (raw)
Hello,
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 :-)
For reference, the testsuite output on a BSD UNIX system looks like:
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-basics.exp ...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-break.exp ...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-console.exp ...
FAIL: gdb.mi/mi-console.exp: Hello message (timeout)
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-disassemble.exp
...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-eval.exp ...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-hack-cli.exp ...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-read-memory.exp
...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-regs.exp ...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-return.exp ...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-simplerun.exp ...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-stack.exp ...
FAIL: gdb.mi/mi-stack.exp: stack args listing 0
FAIL: gdb.mi/mi-stack.exp: stack args listing 1
FAIL: gdb.mi/mi-stack.exp: stack info-depth
FAIL: gdb.mi/mi-stack.exp: stack info-depth 99
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-stepi.exp ...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-until.exp ...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-var-block.exp ...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-var-child.exp ...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-var-cmd.exp ...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-var-display.exp
...
Running /home/scratch/GDB/src/gdb/testsuite/gdb.mi/mi-watch.exp ...
FAIL: gdb.mi/mi-watch.exp: wp out of scope (2)
=== gdb Summary ===
# of expected passes 486
# of unexpected failures 6
# of expected failures 14
Hmm, thinking about it, 500 additional tests is pretty impressive! Well
done Elena and Fernando!
Andrew
next 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 [this message]
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
[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=3AA2FA18.79205BFE@cygnus.com \
--to=ac131313@cygnus.com \
--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