public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/27786] New: FAIL: gdb.base/valgrind-infcall-2.exp: target remote for vgdb (timeout)
@ 2021-04-28 18:15 vries at gcc dot gnu.org
2021-04-29 11:47 ` [Bug testsuite/27786] " vries at gcc dot gnu.org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: vries at gcc dot gnu.org @ 2021-04-28 18:15 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27786
Bug ID: 27786
Summary: FAIL: gdb.base/valgrind-infcall-2.exp: target remote
for vgdb (timeout)
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
I'm seeing this regression:
...
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)
...
I can fix the regression by reverting the testsuite/lib/valgrind.exp part of
6d5702a5eb3 "Fix test case gdb.base/valgrind-bt.exp."
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug testsuite/27786] FAIL: gdb.base/valgrind-infcall-2.exp: target remote for vgdb (timeout)
2021-04-28 18:15 [Bug testsuite/27786] New: FAIL: gdb.base/valgrind-infcall-2.exp: target remote for vgdb (timeout) vries at gcc dot gnu.org
@ 2021-04-29 11:47 ` vries at gcc dot gnu.org
2021-04-29 21:32 ` cvs-commit at gcc dot gnu.org
2021-04-29 21:33 ` vries at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: vries at gcc dot gnu.org @ 2021-04-29 11:47 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27786
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Tentative patch:
https://sourceware.org/pipermail/gdb-patches/2021-April/178335.html
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug testsuite/27786] FAIL: gdb.base/valgrind-infcall-2.exp: target remote for vgdb (timeout)
2021-04-28 18:15 [Bug testsuite/27786] New: FAIL: gdb.base/valgrind-infcall-2.exp: target remote for vgdb (timeout) vries at gcc dot gnu.org
2021-04-29 11:47 ` [Bug testsuite/27786] " vries at gcc dot gnu.org
@ 2021-04-29 21:32 ` cvs-commit at gcc dot gnu.org
2021-04-29 21:33 ` vries at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2021-04-29 21:32 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27786
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=3f334074870230900da2ddec0556c9b4a6d55249
commit 3f334074870230900da2ddec0556c9b4a6d55249
Author: Tom de Vries <tdevries@suse.de>
Date: Thu Apr 29 23:32:20 2021 +0200
[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.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug testsuite/27786] FAIL: gdb.base/valgrind-infcall-2.exp: target remote for vgdb (timeout)
2021-04-28 18:15 [Bug testsuite/27786] New: FAIL: gdb.base/valgrind-infcall-2.exp: target remote for vgdb (timeout) vries at gcc dot gnu.org
2021-04-29 11:47 ` [Bug testsuite/27786] " vries at gcc dot gnu.org
2021-04-29 21:32 ` cvs-commit at gcc dot gnu.org
@ 2021-04-29 21:33 ` vries at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: vries at gcc dot gnu.org @ 2021-04-29 21:33 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27786
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |11.1
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Patch fixing test-case committed, marking resolved-fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-04-29 21:33 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-28 18:15 [Bug testsuite/27786] New: FAIL: gdb.base/valgrind-infcall-2.exp: target remote for vgdb (timeout) vries at gcc dot gnu.org
2021-04-29 11:47 ` [Bug testsuite/27786] " vries at gcc dot gnu.org
2021-04-29 21:32 ` cvs-commit at gcc dot gnu.org
2021-04-29 21:33 ` vries at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).