Tom de Vries 3f33407487 [gdb/testsuite] Fix timeout in gdb.base/valgrind-infcall-2.exp ... Since commit 6d5702a5eb "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.		2021-04-29 23:32:20 +02:00
..
ada.exp
append_gdb_boards_dir.exp
attributes.h
build-piece.exp
cache.exp
check-test-names.exp
cl_util.c
cl_util.h
compile-support.exp
compiler.c
compiler.cc
completion-support.exp
cp-support.exp
d-support.exp
data-structures.exp
dtrace.exp
dwarf.exp
fortran.exp
future.exp
gdb-guile.exp
gdb-python.exp
gdb-utils.exp	gdb: process early initialization files and command line options	2021-04-15 10:34:09 +01:00
gdb.exp	Fix timeout with maint print objfiles	2021-04-27 20:42:07 -03:00
gdbserver-support.exp
gen-perf-test.exp
gnat_debug_info_test.adb
go.exp
jit-elf-helpers.exp
memory.exp
mi-support.exp
my-syscalls.h
my-syscalls.S
objc.exp
opencl_hostapp.c
opencl_kernel.cl
opencl.exp
pascal.exp
pdtrace.in
perftest.exp
prelink-support.exp
prompt.exp
range-stepping-support.exp
read1.c
rust-support.exp
selftest-support.exp
set_unbuffered_mode.c
sym-info-cmds.exp
trace-support.exp
tuiterm.exp
unbuffer_output.c
valgrind.exp	[gdb/testsuite] Fix timeout in gdb.base/valgrind-infcall-2.exp	2021-04-29 23:32:20 +02:00