aboutsummaryrefslogtreecommitdiff
path: root/gdb/ada-lang.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2020-03-11 14:58:59 +0100
committerTom de Vries <tdevries@suse.de>2020-03-11 14:58:59 +0100
commit7462c383f9849aab40f156854a72f0a93305124a (patch)
tree162325a798112f5d797940119e63c1e8331a9055 /gdb/ada-lang.c
parent1c6c46a012a43aefb6183fa2dd16ec6db5751aa3 (diff)
downloadgdb-7462c383f9849aab40f156854a72f0a93305124a.zip
gdb-7462c383f9849aab40f156854a72f0a93305124a.tar.gz
gdb-7462c383f9849aab40f156854a72f0a93305124a.tar.bz2
[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.
Diffstat (limited to 'gdb/ada-lang.c')
0 files changed, 0 insertions, 0 deletions