public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29659] [gdb/testsuite] local-remote-host timeouts with bracketed-paste
Date: Mon, 17 Oct 2022 13:06:31 +0000 [thread overview]
Message-ID: <bug-29659-4717-Gt0VkpQA5A@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29659-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29659
--- Comment #11 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #10)
> And we have a similar problem with DEBUGINFOD_URLS.
Fixed by:
...
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index bfa9fec628e..5c9d9f84da3 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -5863,6 +5863,8 @@ proc default_gdb_init { test_file_name } {
# If DEBUGINFOD_URLS is set, gdb will try to download sources and
# debug info for f.i. system libraries. Prevent this.
unset -nocomplain ::env(DEBUGINFOD_URLS)
+ global INTERNAL_GDBFLAGS
+ append INTERNAL_GDBFLAGS " -iex \"set debuginfod enabled off\""
# Ensure that GDBHISTFILE and GDBHISTSIZE are removed from the
# environment, we don't want these modifications to the history
...
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-10-17 13:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 8:20 [Bug testsuite/29659] New: " vries at gcc dot gnu.org
2022-10-07 8:22 ` [Bug testsuite/29659] " vries at gcc dot gnu.org
2022-10-07 8:35 ` vries at gcc dot gnu.org
2022-10-07 10:06 ` vries at gcc dot gnu.org
2022-10-07 10:09 ` vries at gcc dot gnu.org
2022-10-08 17:23 ` tromey at sourceware dot org
2022-10-09 8:56 ` vries at gcc dot gnu.org
2022-10-10 16:13 ` tromey at sourceware dot org
2022-10-12 4:04 ` vries at gcc dot gnu.org
2022-10-17 13:02 ` vries at gcc dot gnu.org
2022-10-17 13:05 ` vries at gcc dot gnu.org
2022-10-17 13:06 ` vries at gcc dot gnu.org [this message]
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-29659-4717-Gt0VkpQA5A@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: link
Be 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).