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

This commit is contained in:
Andrew Cagney 2000-03-04 03:01:38 +00:00
parent 082faf240e
commit 76c520e05c
2 changed files with 11 additions and 0 deletions

View file

@ -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> 2000-02-01 Elena Zannoni <ezannoni@kwikemart.cygnus.com>
* mi-support.exp (mi_gdb_start): Update to recognize start up * mi-support.exp (mi_gdb_start): Update to recognize start up

View file

@ -130,6 +130,11 @@ proc mi_gdb_start { } {
remote_close host; remote_close host;
return -1; 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 { timeout {
perror "(timeout) GDB never initialized after 10 seconds." perror "(timeout) GDB never initialized after 10 seconds."
remote_close host; remote_close host;