summaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.base
diff options
context:
space:
mode:
authorJim Blandy <jimb@codesourcery.com>2002-07-19 00:02:34 +0000
committerJim Blandy <jimb@codesourcery.com>2002-07-19 00:02:34 +0000
commit263eb64edc2993eaf847dc80e1351df707badec2 (patch)
treeb4daa7253fcf75c73438abf5773170460def054a /gdb/testsuite/gdb.base
parent939823b24f700a21a30d47a385fd03461d275c8f (diff)
downloadgdb-263eb64edc2993eaf847dc80e1351df707badec2.tar.gz
* gdb.base/ending-run.exp: Don't expect to see the program end in
some orderly fashion when we're running on a real stand-alone board.
Diffstat (limited to 'gdb/testsuite/gdb.base')
-rw-r--r--gdb/testsuite/gdb.base/ending-run.exp7
1 files changed, 6 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.base/ending-run.exp b/gdb/testsuite/gdb.base/ending-run.exp
index 656601efc98..69f2b26917c 100644
--- a/gdb/testsuite/gdb.base/ending-run.exp
+++ b/gdb/testsuite/gdb.base/ending-run.exp
@@ -229,7 +229,12 @@ gdb_expect {
timeout { fail "step out of main (hang or timeout on step at end 1)" }
}
-if {![target_info exists use_cygmon] || ![target_info use_cygmon]} {
+# When we're talking to a program running on a real stand-alone board,
+# every BSP's exit function behaves differently, so there's no single
+# way to tell whether we've exited gracefully or not. So don't run
+# these tests when use_gdb_stub is set, or when we're running under Cygmon.
+if {! [target_info exists use_gdb_stub]
+ && (! [target_info exists use_cygmon] || ! [target_info use_cygmon])} {
global program_exited;
if {[eval expr $program_exited == 0]} {
send_gdb "n\n"