[pushed,gdb/testsuite] Add note to 'Race detection' entry in README
Commit Message
The original change was created by Tom de Vries.
Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/762
......................................................................
[gdb/testsuite] Add note to 'Race detection' entry in README
Add note to 'Race detection' entry in README about the possibility that
check-read1 makes failing tests pass.
gdb/testsuite/ChangeLog:
2020-02-04 Tom de Vries <tdevries@suse.de>
* README (Race detection): Add note.
Change-Id: I12ef2f0ec35abc5a0221585bf30e5f4f0616aa7c
---
M gdb/testsuite/ChangeLog
M gdb/testsuite/README
2 files changed, 11 insertions(+), 0 deletions(-)
@@ -1,5 +1,9 @@
2020-02-04 Tom de Vries <tdevries@suse.de>
+ * README (Race detection): Add note.
+
+2020-02-04 Tom de Vries <tdevries@suse.de>
+
* lib/gdb.exp (inferior_exited_re): Use "\[^\n\r\]*" instead of ".*".
2020-02-04 Tom de Vries <tdevries@suse.de>
@@ -352,6 +352,13 @@
make -j10 check-read1 TESTS="*/paginate-*.exp"
make -j10 check READ1="1"
+Note: While the intention is to detect races and make otherwise passing tests
+fail, it can also have the effect of making otherwise failing tests pass.
+This happens f.i. if the test is trying to match a gdb prompt using an end of
+input marker "${gdb_prompt} $" and there is output after the gdb prompt. This
+may either pass or fail in normal operation, but using check-read1 will ensure
+that it passes.
+
Testsuite Configuration
***********************