btrace, testsuite: fix extended-remote non-stop test

With --target_board=native-extended-gdbserver non-stop tests are failing with

    UNTESTED: gdb.btrace/non-stop.exp: failed to run to main

Fix that by adding '-ex "set non-stop on"' to GDBFLAGS before restarting.

testsuite/
	* gdb.btrace/non-stop.exp: Add '-ex "set non-stop on"' to GDBFLAGS.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index d22b16e..3e0a5da 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,5 +1,10 @@
 2017-02-01  Markus Metzger  <markus.t.metzger@intel.com>
 
+       * gdb.btrace/non-stop.exp: Add '-ex "set non-stop on"' to
+       GDBFLAGS.
+
+2017-02-01  Markus Metzger  <markus.t.metzger@intel.com>
+
        * gdb.btrace/buffer-size.exp: Add unsupported/untested message if
        the test is skipped.
        * gdb.btrace/data.exp: Likewise.

diff --git a/gdb/testsuite/gdb.btrace/non-stop.exp b/gdb/testsuite/gdb.btrace/non-stop.exp
index cda15e2..a671b9c 100644 (file)
--- a/gdb/testsuite/gdb.btrace/non-stop.exp
+++ b/gdb/testsuite/gdb.btrace/non-stop.exp
@@ -25,9 +25,11 @@ if {[gdb_compile_pthreads "$srcdir/$subdir/$srcfile" "$binfile" executable {debu
     untested "failed to prepare"
     return -1
 }
-clean_restart $testfile
 
-gdb_test_no_output "set non-stop on"
+save_vars { GDBFLAGS } {
+    append GDBFLAGS " -ex \"set non-stop on\""
+    clean_restart $testfile
+}
 
 if ![runto_main] {
     untested "failed to run to main"