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/28561] [gdb/testsuite] Error due to not reading \r\n at end of mi prompt Date: Mon, 08 Nov 2021 13:09:25 +0000 [thread overview] Message-ID: <bug-28561-4717-w7d7iH8HSe@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28561-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28561 --- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> --- Created attachment 13767 --> https://sourceware.org/bugzilla/attachment.cgi?id=13767&action=edit log for second error -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-08 13:09 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-08 12:54 [Bug testsuite/28561] New: [gdb/testsuite] Error due to not reading \n " vries at gcc dot gnu.org 2021-11-08 12:56 ` [Bug testsuite/28561] [gdb/testsuite] Error due to not reading \r\n " vries at gcc dot gnu.org 2021-11-08 13:05 ` vries at gcc dot gnu.org 2021-11-08 13:09 ` vries at gcc dot gnu.org [this message] 2022-05-09 7:18 ` luis.machado at arm dot com 2022-05-09 8:36 ` vries at gcc dot gnu.org 2022-05-09 10:15 ` luis.machado at arm dot com 2022-05-16 9:14 ` mark at klomp dot org 2022-05-16 9:25 ` mark at klomp dot org 2022-05-30 16:18 ` thiago.bauermann at linaro dot org 2022-05-31 8:40 ` mark at klomp dot org 2022-05-31 8:42 ` mark at klomp dot org 2022-05-31 9:07 ` vries at gcc dot gnu.org 2022-05-31 9:52 ` luis.machado at arm dot com
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-28561-4717-w7d7iH8HSe@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).