This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[rfa/gdb.mi] Fail (known bug) when ``Hello''
- To: GDB Patches <gdb-patches at sourceware dot cygnus dot com>
- Subject: [rfa/gdb.mi] Fail (known bug) when ``Hello''
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Mon, 19 Mar 2001 10:42:49 -0500
G'day,
The attatched changes the ``Hello'' test to recognize raw (instead of
MI's console) output reporting it as a fail. Without the patch, the
test fails, eventually, via a timeout.
The test work does work on remote targets. Fixing it on a native target
is hard - there are too many ducks and I'm having fun getting just one
of them to stand in a straight line :-)
Andrew
2001-03-19 Andrew Cagney <ac131313@redhat.com>
* gdb.mi/mi-console.exp: Document ``Hello'' as a known bug.
Index: gdb.mi/mi-console.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.mi/mi-console.exp,v
retrieving revision 1.1
diff -p -r1.1 mi-console.exp
*** mi-console.exp 2000/02/23 00:25:43 1.1
--- mi-console.exp 2001/03/19 15:31:04
*************** gdb_expect {
*** 78,83 ****
--- 78,94 ----
gdb_expect {
-re "@\"H\"\r\n.*@\"e\"\r\n.*@\"l\"\r\n.*@\"l\"\r\n.*@\"o\"\r\n.*@\" \"\r\n.*@\"\\\\\\\\\"\r\n.*@\"\\\\\"\"\r\n.*@\"!\"\r\n.*@\"\\\\r\"\r\n.*@\"\\\\n\"\r\n" {
pass "Hello message"
+ }
+ -re "Hello" {
+
+ # Probably a native system where GDB doesn't have direct
+ # control over the inferior console.
+ # For this to work, GDB would need to run the inferior process
+ # under a PTY and then use the even-loops ability to wait on
+ # multiple event sources to channel the output back through the
+ # MI.
+
+ fail "Hello message (known bug)"
}
timeout {
fail "Hello message (timeout)"