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/29726] [gdb] FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=: action=delete: connection to GDBserver succeeded Date: Thu, 27 Oct 2022 08:17:23 +0000 [thread overview] Message-ID: <bug-29726-4717-Lvpgc6V3is@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29726-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29726 --- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> --- I tried to reproduce using: ... $ git diff diff --git a/gdb/testsuite/gdb.server/connect-with-no-symbol-file.exp b/gdb/testsuite/gdb.s erver/connect-with-no-symbol-file.exp index d45e958a529..d3e9f96f46a 100644 --- a/gdb/testsuite/gdb.server/connect-with-no-symbol-file.exp +++ b/gdb/testsuite/gdb.server/connect-with-no-symbol-file.exp @@ -93,12 +93,17 @@ proc connect_no_symbol_file { sysroot action } { # Make sure we have the original symbol file in a safe place to copy from. gdb_remote_download host $binfile $binfile.bak -# Start with no executable loaded. -clean_restart - -# Run the test with different permutations. -foreach_with_prefix sysroot {"" "target:"} { - foreach_with_prefix action {"permission" "delete"} { - connect_no_symbol_file $sysroot $action +set n 1000 +for {set i 1} {$i <= $n} {incr i} { + # Start with no executable loaded. + clean_restart + + with_test_prefix $i { + # Run the test with different permutations. + foreach_with_prefix sysroot {"" "target:"} { + foreach_with_prefix action {"permission" "delete"} { + connect_no_symbol_file $sysroot $action + } + } } } ... but that runs into a hang after ~200 iterations: ... builtin_spawn /home/vries/gdb_versions/devel/build/gdb/testsuite/../../gdb/../gdbserver/gdbserver --once localhost:3151 /home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/connect-with-no-symbol-file/connect-with-no-symbol-file^M spawn of /home/vries/gdb_versions/devel/build/gdb/testsuite/../../gdb/../gdbserver/gdbserver --once localhost:3151 /home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.server/connect-with-no-symbol-file/connect-with-no-symbol-file failed ERROR: tcl error sourcing /home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.server/connect-with-no-symbol-file.exp. ERROR: Timeout waiting for gdbserver response. ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-27 8:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-27 7:19 [Bug testsuite/29726] New: " vries at gcc dot gnu.org 2022-10-27 7:21 ` [Bug testsuite/29726] " vries at gcc dot gnu.org 2022-10-27 7:45 ` vries at gcc dot gnu.org 2022-10-27 8:17 ` vries at gcc dot gnu.org [this message] 2022-10-27 8:33 ` vries at gcc dot gnu.org 2022-10-27 9:04 ` vries at gcc dot gnu.org 2022-10-27 9:26 ` luis.machado at arm dot com 2022-10-27 14:56 ` [Bug testsuite/29726] [gdb/testsuite] " 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-29726-4717-Lvpgc6V3is@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).