aboutsummaryrefslogtreecommitdiff
path: root/gdbsupport
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2020-03-15 10:43:43 +0100
committerTom de Vries <tdevries@suse.de>2020-03-15 10:43:43 +0100
commiteaeaf44cfdc9a4096a0dd52fa0606f29d4bfd48e (patch)
tree14c6421249eecab364e76099b1c1abe5c65a51ec /gdbsupport
parent3293bbaffac9a22fc6d1a08ac6602a4a63b5e68b (diff)
downloadgdb-eaeaf44cfdc9a4096a0dd52fa0606f29d4bfd48e.zip
gdb-eaeaf44cfdc9a4096a0dd52fa0606f29d4bfd48e.tar.gz
gdb-eaeaf44cfdc9a4096a0dd52fa0606f29d4bfd48e.tar.bz2
[gdb/testsuite] Fix check-read1 FAIL with gdb.base/maint.exp
When running test-case gdb.base/maint.exp with check-read1, I run into: ... FAIL: gdb.base/maint.exp: (timeout) maint print objfiles ... The FAIL happens because command output contains long lines like this: ... file1 at $hex, file2 at $hex, ..., $file$n at $hex, ... F.i., such a line for libc.so.debug contains 82000 chars. Fix this this by reading long lines bit by bit. Also, replace the testing of the command output formulated using a gdb_send combined with gdb_expect-in-a-loop, with a regular gdb_test_multiple with exp_continue. Tested on x86_64-linux, with make targets check and check-read1. gdb/testsuite/ChangeLog: 2020-03-15 Tom de Vries <tdevries@suse.de> * gdb.base/maint.exp: Use exp_continue in long lines for "maint print objfiles".
Diffstat (limited to 'gdbsupport')
0 files changed, 0 insertions, 0 deletions