diff options
| author | Tom de Vries <tdevries@suse.de> | 2021-04-29 23:32:20 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2021-04-29 23:32:20 +0200 |
| commit | 3f334074870230900da2ddec0556c9b4a6d55249 (patch) | |
| tree | 785379f4d54ff132654ddeb1c93525263768c92b /gdb/testsuite/lib | |
| parent | e197dfae62d741b8cd147bab888183c7c90f2a88 (diff) | |
| download | gdb-3f334074870230900da2ddec0556c9b4a6d55249.zip gdb-3f334074870230900da2ddec0556c9b4a6d55249.tar.gz gdb-3f334074870230900da2ddec0556c9b4a6d55249.tar.bz2 | |
[gdb/testsuite] Fix timeout in gdb.base/valgrind-infcall-2.exp
Since commit 6d5702a5eb3 "Fix test case gdb.base/valgrind-bt.exp" I run into:
...
FAIL: gdb.base/valgrind-infcall-2.exp: target remote for vgdb (timeout)
FAIL: gdb.base/valgrind-infcall-2.exp: monitor v.set gdb_output (timeout)
...
The commit adds this line in proc vgdb_start:
...
set vgdbcmd "set remotetimeout 3"
...
which has no effect given that the value of var vgdbcmd is not used before
it's overwritten. We can fix this by doing instead:
...
set_remotetimeout 3
...
The FAIL I'm observing is fixed by increasing the remotetimeout value to 4.
Tested on x86_64-linux.
gdb/testsuite/ChangeLog:
2021-04-29 Tom de Vries <tdevries@suse.de>
PR testsuite/27786
* lib/valgrind.exp (vgdb_start): Use set_remotetimeout. Increase
remotetimeout to 4.
Diffstat (limited to 'gdb/testsuite/lib')
| -rw-r--r-- | gdb/testsuite/lib/valgrind.exp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/lib/valgrind.exp b/gdb/testsuite/lib/valgrind.exp index caabeda..bba338f 100644 --- a/gdb/testsuite/lib/valgrind.exp +++ b/gdb/testsuite/lib/valgrind.exp @@ -82,7 +82,7 @@ proc vgdb_start { {active_at_startup 1} } { clean_restart $testfile - set vgdbcmd "set remotetimeout 3" + set_remotetimeout 4 # Make sure we're disconnected, in case we're testing with the # native-extended-gdbserver board, where gdb_start/gdb_load spawn |