summaryrefslogtreecommitdiff
path: root/gdb/testsuite/ChangeLog
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2015-11-30 16:05:19 +0000
committerPedro Alves <palves@redhat.com>2015-11-30 18:40:07 +0000
commit09df4675f2e4f8f098954f9a38f44d12089f1c4e (patch)
treea80fcd74e40003df85edc07150f309f1a8aae24c /gdb/testsuite/ChangeLog
parent56cf4bed5354769d7352c5cf4e054a346d2553cd (diff)
downloadbinutils-gdb-09df4675f2e4f8f098954f9a38f44d12089f1c4e.tar.gz
Make dprintf-non-stop.exp cope with remote testing
Testing with the extended-remote board with "maint set target-non-stop on" shows a dprintf-non-stop.exp regression. The issue is simply that the test is expecting output that is only valid for the native target: native: [process 8676] #1 stopped. remote: [Thread 8900.8900] #1 stopped. In order to expose this without "maint set target-non-stop on", this restarts gdb with non-stop mode already enabled. gdb/testsuite/ChangeLog: 2015-11-30 Pedro Alves <palves@redhat.com> * gdb.base/dprintf-non-stop.exp: Use build_executable instead of prepare_for_testing. Start gdb with "set non-stop on" appended to GDBFLAGS. Lax expected stop output.
Diffstat (limited to 'gdb/testsuite/ChangeLog')
-rw-r--r--gdb/testsuite/ChangeLog6
1 files changed, 6 insertions, 0 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 2fddb7cc15f..02a9a07b1a2 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,9 @@
+2015-11-30 Pedro Alves <palves@redhat.com>
+
+ * gdb.base/dprintf-non-stop.exp: Use build_executable instead of
+ prepare_for_testing. Start gdb with "set non-stop on" appended to
+ GDBFLAGS. Lax expected stop output.
+
2015-11-27 Yao Qi <yao.qi@linaro.org>
* gdb.arch/arm-neon.exp: New.