mirrors/binutils-gdb
0
0
Fork 0
mirror of https://sourceware.org/git/binutils-gdb.git synced 2024-11-27 03:54:41 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

* gdb.base/ending-run.exp: Don't expect to see the program end in

Browse Source 
some orderly fashion when we're running on a real stand-alone
board.
This commit is contained in:
Jim Blandy 2002-07-19 00:02:34 +00:00
parent 08dcdf1c0c
commit 0f815cdf7e
2 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/testsuite/ChangeLog
View File

@ -1,5 +1,9 @@
2002-07-18 Jim Blandy <jimb@redhat.com>
* 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.
* gdb.base/interrupt.exp: Correct logic for skipping tests on
targets that don't support interrupts.

7
gdb/testsuite/gdb.base/ending-run.exp
View File

@ -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"