This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[PATCH 0/6] Fix several cases of racy output matching
- From: Pedro Alves <palves at redhat dot com>
- To: gdb-patches at sourceware dot org
- Date: Thu, 26 Oct 2017 18:42:21 +0100
- Subject: [PATCH 0/6] Fix several cases of racy output matching
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx08.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx08.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=palves at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 4F734C07FC1B
After <https://sourceware.org/ml/gdb-patches/2017-10/msg00751.html>, I
had the bright idea of running the whole testsuite with "make
check-read1", and that exposed a number of problems.
This fixes a good chunk of those. (There are more in at least gdb.mi/
and gdb.python/.)
Pedro Alves (6):
Fix racy output matching in gdb.asm/asm-source.exp
Fix racy output matching in gdb.base/completion.exp
Fix racy output matching in gdb.base/memattr.exp
Fix racy output matching in gdb.base/cpcompletion.exp
Fix racy output matching in gdb.base/multi-attach.exp,
gdb.server/ext-{attach, restart, ext-run}.exp
Fix racy output matching in gdb.tui/tui-completion.exp
gdb/testsuite/gdb.asm/asm-source.exp | 2 +-
gdb/testsuite/gdb.base/completion.exp | 86 +++++++++++++-------------------
gdb/testsuite/gdb.base/memattr.exp | 12 ++---
gdb/testsuite/gdb.cp/cpcompletion.exp | 2 +-
gdb/testsuite/gdb.multi/multi-attach.exp | 4 +-
gdb/testsuite/gdb.server/ext-attach.exp | 2 +-
gdb/testsuite/gdb.server/ext-restart.exp | 2 +-
gdb/testsuite/gdb.server/ext-run.exp | 2 +-
gdb/testsuite/gdb.server/ext-wrapper.exp | 2 +-
gdb/testsuite/gdb.tui/completion.exp | 36 +++++++------
10 files changed, 65 insertions(+), 85 deletions(-)
--
2.5.5