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/29669] New: [gdb/testsuite] silent timeout with host board local-remote-host-notty Date: Tue, 11 Oct 2022 15:05:58 +0000 [thread overview] Message-ID: <bug-29669-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29669 Bug ID: 29669 Summary: [gdb/testsuite] silent timeout with host board local-remote-host-notty 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 tried to run the gdb testsuite, test-cases gdb.server/*.exp using host board local-remote-host-notty and noticed in the first test-case gdb.server/stop-reply-no-thread-multi.exp a silent timeout on: ... (gdb) kill^M (gdb) The program is not being run.^M ... I can reproduce this standalone using this command, which usually produces the expected: ... $ /usr/bin/ssh -l vries 127.0.0.1 ~/gdb_versions/devel/gdb.sh -ex \"maint set target-non-stop off\" -ex kill The program is not being run. (gdb) q $ ... But sometimes: ... $ /usr/bin/ssh -l vries 127.0.0.1 ~/gdb_versions/devel/gdb.sh -ex \"maint set target-non-stop off\" -ex kill (gdb) The program is not being run. q $ ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-10-11 15:05 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-11 15:05 vries at gcc dot gnu.org [this message] 2022-10-11 15:53 ` [Bug testsuite/29669] " vries at gcc dot gnu.org 2022-10-14 6:09 ` vries at gcc dot gnu.org 2022-10-14 9:29 ` vries at gcc dot gnu.org 2022-10-14 18:02 ` 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-29669-4717@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).