public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/27786] FAIL: gdb.base/valgrind-infcall-2.exp: target remote for vgdb (timeout) Date: Thu, 29 Apr 2021 21:32:24 +0000 [thread overview] Message-ID: <bug-27786-4717-ziEt8aXb4R@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27786-4717@http.sourceware.org/bugzilla/> 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.
next prev parent reply other threads:[~2021-04-29 21:32 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-28 18:15 [Bug testsuite/27786] New: " 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 [this message] 2021-04-29 21:33 ` vries at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-27786-4717-ziEt8aXb4R@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).