From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 73C213857B9B; Tue, 11 Oct 2022 15:05:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 73C213857B9B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1665500759; bh=BMI8qCDj3hM7RaLUM3yco2yF/ca9OUWiDg6qtS64XaI=; h=From:To:Subject:Date:From; b=tpQOLjPCdgi3QkaVUxHRjqGfhxSYM18OBsXoKYPfoFh0L9/ac+3XGMYzly075J+Yp TYu7W5dG3MILedDUfY04Vm454UzRepe2qLnPmPcTnx1m9N+fvLxYXu4CJ96mfjEBt2 RHpvMnupZXHmNycehkWU2ozcgPjZ1JGsBCQ06q2Q= From: "vries at gcc dot gnu.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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29669 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 bo= ard 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 s= et target-non-stop off\" -ex kill=20 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 s= et target-non-stop off\" -ex kill=20 (gdb) The program is not being run. q $ ... --=20 You are receiving this mail because: You are on the CC list for the bug.=