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/29036] [gdb][testcase-failure, taskset] FAIL: gdb.mi/mi-multi-commands.exp: args=separate-mi-tty: look for first command output, command length 234 Date: Fri, 29 Apr 2022 09:33:50 +0000 [thread overview] Message-ID: <bug-29036-4717-ArkHye3mDu@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29036-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29036 --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- Also ran into this with check-read1. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-29 9:33 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-07 13:16 [Bug gdb/29036] New: " vries at gcc dot gnu.org 2022-04-29 9:33 ` vries at gcc dot gnu.org [this message] 2022-04-29 9:37 ` [Bug gdb/29036] " vries at gcc dot gnu.org 2022-04-29 11:15 ` aburgess at redhat dot com 2022-05-02 9:20 ` vries at gcc dot gnu.org 2022-05-09 15:57 ` cvs-commit at gcc dot gnu.org 2022-05-23 13:49 ` [Bug testsuite/29036] " 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-29036-4717-ArkHye3mDu@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).