testsuite: Fix gdb.base/bang.exp for remote stubs without exit

Some remote stubs do not have a proper exit() function implementation.
gdb.base/bang.exp was failing on those targets due to timeout.  With
this patch bang.exp uses already defined library procedures to handle
this situation gracefully without breaking native targets.

Tested with x86_64 (unix, native-gdbserver) and with arc-*-elf32.

gdb/testsuite/ChangeLog:

2013-10-25  Anton Kolesov  <Anton.Kolesov@synopsys.com>  (tiny change)

	* gdb.base/bang.exp: Use gdb_continue_to_end to properly support
	remote stubs where exit() behaviour is unreliable.
This commit is contained in:
Anton Kolesov 2013-10-09 12:58:14 +04:00 committed by Tom Tromey
parent 686d4defdf
commit 38095c27fb
2 changed files with 7 additions and 9 deletions

View file

@ -1,3 +1,8 @@
2013-10-25 Anton Kolesov <Anton.Kolesov@synopsys.com> (tiny change)
* gdb.base/bang.exp: Use gdb_continue_to_end to properly support
remote stubs where exit() behaviour is unreliable.
2013-10-25 Pedro Alves <palves@redhat.com>
* gdb.cp/m-static.exp: Adjust expected output of printing a

View file

@ -26,12 +26,5 @@ if {[prepare_for_testing $testfile.exp ${testfile}! $srcfile \
# Verify that we can run the program and that it terminates normally.
gdb_run_cmd
gdb_expect {
-re ".*$inferior_exited_re normally.*$gdb_prompt $" {
pass "run program"
}
timeout {
fail "run program (timeout)"
}
}
runto_main
gdb_continue_to_end "" continue 1