Call gdb_exit before gdb_skip_xml_test on gdb.base/catch-syscall.exp

The gdb_skip_xml_test procedure explicitly says that it cannot be
invoked when GDB is running.  However, the testcase for "catch
syscall" is wrongly doing that, which is causing a failure on
native-extended-gdbserver tests:

  new FAIL: gdb.base/catch-syscall.exp: set tdesc filename /home/gdb-buildbot/fedora-x86-64-3/fedora-x86-64-native-extended-gdbserver-m32/build/gdb/testsuite/outputs/gdb.base/catch-syscall/trivial.xml (got interactive prompt)

This obvious commit fixes this, by calling gdb_exit before gdb_skip_xml_test.

Checked in as obvious.

gdb/testsuite/ChangeLog
2015-07-24  Sergio Durigan Junior  <sergiodj@redhat.com>

	* gdb.base/catch-syscall.exp: Call gdb_exit before
	gdb_skip_xml_test.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 8e878f1893cb89f3b881ffd0e6f5e50a1a97b4f6..b0e8e4b890d737720ab07f095cea12e6e07533ad 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,8 @@
+2015-07-24  Sergio Durigan Junior  <sergiodj@redhat.com>
+
+       * gdb.base/catch-syscall.exp: Call gdb_exit before
+       gdb_skip_xml_test.
+
 2015-07-24  Pedro Alves  <palves@redhat.com>
 
        * gdb.python/py-events.exp: Accept output between the stop event

diff --git a/gdb/testsuite/gdb.base/catch-syscall.exp b/gdb/testsuite/gdb.base/catch-syscall.exp
index 40ca148c73663ec3fb2723b83a86de528462ae1d..499da322267c54bb1213146591174257c423e1bb 100644 (file)
--- a/gdb/testsuite/gdb.base/catch-syscall.exp
+++ b/gdb/testsuite/gdb.base/catch-syscall.exp
@@ -509,6 +509,7 @@ setup_all_syscalls
 fill_all_syscalls_numbers
 
 # Execute the tests, using XML support
+gdb_exit
 if { ![gdb_skip_xml_test] } {
   clean_restart $binfile
   do_syscall_tests