From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BC9703858CDA; Sat, 11 Mar 2023 15:03:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BC9703858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1678547010; bh=gz2MPUW/FJ2e2lmBbnqMc2M9326ERv2hhaUN+OY6j7g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=u7OVOO2OjWsyVH84B9sBwsuQ4/gc9b1aOITAQJz2+8Oa9J2tTdBXXkEbudEj9eR2v EggRbISIEC+jy+shKHP5a8MEYr8Xn9HhbyiKxfvRyhzZ1T1FDzsRYwRleWn4PrEbXO jSynMWgrIFkx/bAHRZoCKg9uhbVaINV86h9zqLG0= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/29833] [gdb] FAIL: gdb.server/monitor-exit-quit.exp: monitor exit Date: Sat, 11 Mar 2023 15:03:28 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb 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: Message-ID: In-Reply-To: References: 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=3D29833 --- Comment #13 from Tom de Vries --- Hmm, with test-case gdb.threads/access-mem-running-thread-exit.exp and targ= et board native-gdbserver I run into: ... (gdb) PASS: gdb.threads/access-mem-running-thread-exit.exp: non-stop: access mem Remote debugging from host ::1, port 35770^M monitor exit^M (gdb) Remote connection closed^M (gdb) WARNING: Timed out waiting for EOF in server after monitor exit ... That looks like the same symptom at least, and it reproduces sometimes when= I run the test-case by itself. --=20 You are receiving this mail because: You are on the CC list for the bug.=