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 gdb/29833] [gdb] FAIL: gdb.server/monitor-exit-quit.exp: monitor exit Date: Sat, 11 Mar 2023 15:03:28 +0000 [thread overview] Message-ID: <bug-29833-4717-9ADqlduvXr@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29833-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29833 --- Comment #13 from Tom de Vries <vries at gcc dot gnu.org> --- Hmm, with test-case gdb.threads/access-mem-running-thread-exit.exp and target 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. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-11 15:03 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-29 7:19 [Bug gdb/29833] New: " vries at gcc dot gnu.org 2022-11-30 8:11 ` [Bug gdb/29833] " vries at gcc dot gnu.org 2022-11-30 9:45 ` vries at gcc dot gnu.org 2022-11-30 12:50 ` simark at simark dot ca 2022-12-01 9:50 ` vries at gcc dot gnu.org 2022-12-01 10:59 ` vries at gcc dot gnu.org 2022-12-01 11:18 ` vries at gcc dot gnu.org 2023-01-06 18:05 ` vries at gcc dot gnu.org 2023-01-07 17:42 ` vries at gcc dot gnu.org 2023-01-09 14:53 ` vries at gcc dot gnu.org 2023-01-09 14:53 ` vries at gcc dot gnu.org 2023-01-10 10:43 ` vries at gcc dot gnu.org 2023-01-10 14:00 ` vries at gcc dot gnu.org 2023-03-11 15:03 ` vries at gcc dot gnu.org [this message] 2024-01-15 9:20 ` vries at gcc dot gnu.org 2024-01-16 7:35 ` [Bug testsuite/29833] " 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-29833-4717-9ADqlduvXr@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).