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/29195] [gdb, gcc-12/m32] FAIL: gdb.mi/mi-var-block.exp: update all vars: cb foo changed (unexpected output) Date: Tue, 07 Jun 2022 14:30:15 +0000 [thread overview] Message-ID: <bug-29195-4717-7RTLEwJaFz@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29195-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29195 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |13.1 --- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> --- https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=bb785a92a88b538831d72e36f2d0fce76e0a32b1 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-07 14:30 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-28 7:42 [Bug gdb/29195] New: " vries at gcc dot gnu.org 2022-05-31 13:41 ` [Bug gdb/29195] " vries at gcc dot gnu.org 2022-05-31 13:41 ` [Bug testsuite/29195] " vries at gcc dot gnu.org 2022-05-31 14:03 ` vries at gcc dot gnu.org 2022-06-07 14:30 ` vries at gcc dot gnu.org [this message] 2022-06-07 14:30 ` 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-29195-4717-7RTLEwJaFz@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).