aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.threads
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2020-03-12 13:51:46 +0100
committerTom de Vries <tdevries@suse.de>2020-03-12 13:51:46 +0100
commite515d67ed61f7c588a3154589a8a25c7bef66d20 (patch)
tree1ea9e2c71a3bf45c08d1f7b04dbd04d03daeb9a4 /gdb/testsuite/gdb.threads
parent307eafd8df3ec820bb62a71324aeed06b86ec050 (diff)
downloadgdb-e515d67ed61f7c588a3154589a8a25c7bef66d20.zip
gdb-e515d67ed61f7c588a3154589a8a25c7bef66d20.tar.gz
gdb-e515d67ed61f7c588a3154589a8a25c7bef66d20.tar.bz2
[gdb/testsuite] Fix internal buffer full error in gdb.fortran/module.exp
With test-case gdb.fortran/module.exp, I run into: ... PASS: gdb.fortran/module.exp: fully qualified name of DW_TAG_constant ERROR: internal buffer is full. UNRESOLVED: gdb.fortran/module.exp: info variables -n ... Fix this by using exp_continue while matching the output of "info variable -n". Tested on x86_64-linux, using make targets check and check-read1. gdb/testsuite/ChangeLog: 2020-03-12 Tom de Vries <tdevries@suse.de> * gdb.fortran/module.exp: Use exp_continue during matching of output of "info variable -n".
Diffstat (limited to 'gdb/testsuite/gdb.threads')
0 files changed, 0 insertions, 0 deletions