]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit - gdb/testsuite/ChangeLog
[gdb/testsuite] Fix timeout in gdb.threads/detach-step-over.exp with readnow
authorTom de Vries <tdevries@suse.de>
Wed, 5 May 2021 13:13:17 +0000 (15:13 +0200)
committerTom de Vries <tdevries@suse.de>
Wed, 5 May 2021 13:13:17 +0000 (15:13 +0200)
commit2f000c80e2f6c2946939b2a7a1ea1c0340626afb
treec6ea57da8e809e1b7a83a31b5fe24de84b63aba0
parent09f83f79f7d7334715e5fca9e89d5a97da5b0bd3
[gdb/testsuite] Fix timeout in gdb.threads/detach-step-over.exp with readnow

When running test-case gdb.threads/detach-step-over.exp with target board
readnow, I run into:
...
Reading symbols from /lib64/libc.so.6...^M
Reading symbols from \
  /usr/lib/debug/lib64/libc-2.26.so-2.26-lp152.26.6.1.x86_64.debug...^M
Expanding full symbols from \
  /usr/lib/debug/lib64/libc-2.26.so-2.26-lp152.26.6.1.x86_64.debug...^M
FAIL: gdb.threads/detach-step-over.exp: \
  breakpoint-condition-evaluation=host: target-non-stop=on: non-stop=on: \
  displaced=off: iter 2: attach (timeout)
...

Fix this by doing exp_continue when encountering the "Reading symbols" or
"Expanding full symbols" lines.

This is still fragile and times out with a higher load, similated f.i. by
stress -c 5.  Fix that by using a timeout factor of 2.

Tested on x86_64-linux.

gdb/testsuite/ChangeLog:

2021-05-05  Tom de Vries  <tdevries@suse.de>

* gdb.threads/detach-step-over.exp: Do exp_continue when encountering
"Reading symbols" or "Expanding full symbols" lines.  Using timeout
factor of 2 for attach.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.threads/detach-step-over.exp