]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit
[gdb/testsuite] Fix FAILs due to verbose in foll-fork.exp
authorTom de Vries <tdevries@suse.de>
Wed, 11 Mar 2020 13:58:59 +0000 (14:58 +0100)
committerTom de Vries <tdevries@suse.de>
Wed, 11 Mar 2020 13:58:59 +0000 (14:58 +0100)
commit7462c383f9849aab40f156854a72f0a93305124a
tree162325a798112f5d797940119e63c1e8331a9055
parent1c6c46a012a43aefb6183fa2dd16ec6db5751aa3
[gdb/testsuite] Fix FAILs due to verbose in foll-fork.exp

When running test-case gdb.base/foll-fork.exp, I see:
...
(gdb) catch fork^M
Catchpoint 2 (fork)^M
Reading in symbols for ../sysdeps/x86/libc-start.c...^M
(gdb) FAIL: gdb.base/foll-fork.exp: explicit child follow, set catch fork
...

The problem is that the test regexp does not expect the "Reading in symbols"
message:
...
    gdb_test "catch fork" "Catchpoint \[0-9\]* \\(fork\\)" \
        "explicit child follow, set catch fork"
...
which is generated due to the verbose setting.

Fix this by allowing the message in the regexp.

Tested on x86_64-linux.

gdb/testsuite/ChangeLog:

2020-03-11  Tom de Vries  <tdevries@suse.de>

* gdb.base/foll-fork.exp: Allow "Reading in symbols" messages.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/foll-fork.exp