summaryrefslogtreecommitdiff
path: root/gdb/testsuite/ChangeLog
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2015-11-30 16:05:23 +0000
committerPedro Alves <palves@redhat.com>2015-11-30 18:42:06 +0000
commit04bf20c5687b102b9a2c2a915d4c400788296a3b (patch)
tree6c6d002ba5aeaec51ea4fbf60830aeac52ef9c06 /gdb/testsuite/ChangeLog
parenta681f9c91372d282229f6d58ba235ef0dd3644fb (diff)
downloadbinutils-gdb-04bf20c5687b102b9a2c2a915d4c400788296a3b.tar.gz
testsuite: Range stepping and non-stop mode
The range-stepping tests fail with "maint set target-non-stop on" mode because exec_cmd_expect_vCont_count doesn't know that in non-stop mode, vCont's reply is simply "OK". gdb/testsuite/ChangeLog: 2015-11-30 Pedro Alves <palves@redhat.com> * lib/range-stepping-support.exp (exec_cmd_expect_vCont_count): Handle non-stop mode vCont replies.
Diffstat (limited to 'gdb/testsuite/ChangeLog')
-rw-r--r--gdb/testsuite/ChangeLog5
1 files changed, 5 insertions, 0 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 02a9a07b1a2..08b5b6fbc75 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,5 +1,10 @@
2015-11-30 Pedro Alves <palves@redhat.com>
+ * lib/range-stepping-support.exp (exec_cmd_expect_vCont_count):
+ Handle non-stop mode vCont replies.
+
+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.