When GDB doesn't recognize the -i=mi option, assume there is no MI support.

diff --git a/gdb/testsuite/gdb.mi/ChangeLog-mi b/gdb/testsuite/gdb.mi/ChangeLog-mi
index 9d4f1ce..4cff05d 100644 (file)
--- a/gdb/testsuite/gdb.mi/ChangeLog-mi
+++ b/gdb/testsuite/gdb.mi/ChangeLog-mi
@@ -1,3 +1,9 @@
+Sat Mar  4 13:55:08 2000  Andrew Cagney  <cagney@b1.cygnus.com>
+
+       From Fri 3 Mar 2000 Peter Schauer:
+       * mi-support.exp (mi_gdb_start): When GDB doesn't recongize -i=mi
+       option, assume no MI support present.
+
 2000-02-01  Elena Zannoni  <ezannoni@kwikemart.cygnus.com>
 
        * mi-support.exp (mi_gdb_start): Update to recognize start up

diff --git a/gdb/testsuite/lib/mi-support.exp b/gdb/testsuite/lib/mi-support.exp
index 7d207df..1cad1b1 100644 (file)
--- a/gdb/testsuite/lib/mi-support.exp
+++ b/gdb/testsuite/lib/mi-support.exp
@@ -130,6 +130,11 @@ proc mi_gdb_start { } {
            remote_close host;
            return -1;
        }
+       -re ".*unrecognized option.*for a complete list of options." {
+           untested "Skip mi tests (not compiled with mi support)."
+           remote_close host;
+           return -1;
+       }
        timeout {
            perror "(timeout) GDB never initialized after 10 seconds."
            remote_close host;