Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Cc: Andrew Cagney <cagney@redhat.com>
Subject: [RFA/mi-testsuite] XFAIL mi*-console.exp
Date: Tue, 02 Apr 2002 16:42:00 -0000	[thread overview]
Message-ID: <20020402194252.A20826@nevyn.them.org> (raw)

These tests are testing for a feature that exists either nowhere or just in
simulators and some remote stubs: that the inferior's output goes through
GDB and is properly encoded by the MI layer.  Since support isn't there for
many remote debugging stubs or for native, I think these two tests should be
XFAIL'd.  Does that make sense, Andrew?  If so, OK to commit this?

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

2002-04-02  Daniel Jacobowitz  <drow@mvista.com>

	* gdb.mi/mi-console.exp: Accept lack of MI-console output as an
	XFAIL.
	* gdb.mi/mi0-console.exp: Likewise.

Index: testsuite/gdb.mi/mi-console.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.mi/mi-console.exp,v
retrieving revision 1.7
diff -u -p -r1.7 mi-console.exp
--- mi-console.exp	2001/08/19 01:23:43	1.7
+++ mi-console.exp	2002/04/03 00:38:09
@@ -92,7 +92,10 @@ gdb_expect {
 	# multiple event sources to channel the output back through the
 	# MI.
 
-	fail "Hello message (known bug)"
+	xfail "Hello message (known limitation)"
+    }
+    -notransfer -re "\r\n$mi_gdb_prompt" {
+	xfail "Hello message (no output)"
     }
     timeout {
 	fail "Hello message (timeout)"
Index: testsuite/gdb.mi/mi0-console.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.mi/mi0-console.exp,v
retrieving revision 1.5
diff -u -p -r1.5 mi0-console.exp
--- mi0-console.exp	2001/08/19 01:23:43	1.5
+++ mi0-console.exp	2002/04/03 00:38:09
@@ -92,7 +92,10 @@ gdb_expect {
 	# multiple event sources to channel the output back through the
 	# MI.
 
-	fail "Hello message (known bug)"
+	xfail "Hello message (known limitation)"
+    }
+    -notransfer -re "\r\n$mi_gdb_prompt" {
+	xfail "Hello message (no output)"
     }
     timeout {
 	fail "Hello message (timeout)"


             reply	other threads:[~2002-04-03  0:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 16:42 Daniel Jacobowitz [this message]
2002-04-02 16:52 ` Michael Snyder
2002-04-02 17:01   ` Daniel Jacobowitz
2002-04-02 17:22     ` Michael Snyder
2002-04-02 17:39       ` Daniel Jacobowitz
2002-04-03  6:14         ` Fernando Nasser
2002-04-04  7:15           ` Fernando Nasser
2002-04-04  8:36             ` Daniel Jacobowitz
2002-04-04 11:09             ` Andrew Cagney
2002-04-03 20:27 ` Andrew Cagney
2002-04-03 21:13   ` Daniel Jacobowitz
2002-04-04 13:49     ` Andrew Cagney
2002-04-04 13:53       ` Daniel Jacobowitz
2002-04-06 15:04         ` Andrew Cagney
2002-04-04 16:55       ` Fernando Nasser
2002-04-05  6:49         ` Andrew Cagney
2002-04-05  7:22           ` Fernando Nasser
2002-04-05  7:23 Michael Elizabeth Chastain

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=20020402194252.A20826@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=cagney@redhat.com \
    --cc=gdb-patches@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