From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB 13.2 (corrective) release -- 2023-05-05 Update
Date: Thu, 11 May 2023 16:19:22 -0600 [thread overview]
Message-ID: <87zg6awlxx.fsf@tromey.com> (raw)
In-Reply-To: <ZFhOIjRsUsIpczjU@adacore.com> (Joel Brobecker via Gdb-patches's message of "Sun, 7 May 2023 18:19:30 -0700")
>>>>> "Joel" == Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org> writes:
Joel> Hi Everyone,
Joel> No real change since our last update a week ago: So far, no known
Joel> blocking issue that we want to fix before we publish GDB 13.2.
Joel> => Target release date: Sat 27 May 2023.
Joel> Please let us know if there are issues that we should consider for
Joel> that release.
I think this one would be reasonable:
https://sourceware.org/bugzilla/show_bug.cgi?id=30271
It's a fairly obvious bug in the new scanner.
I wrote a test case and I'm going to check it in on git master soon.
I set the target milestone on the bug but of course we can change it if
need be.
Tom
next prev parent reply other threads:[~2023-05-11 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 1:19 Joel Brobecker
2023-05-11 22:19 ` Tom Tromey [this message]
2023-05-12 18:52 ` Joel Brobecker
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=87zg6awlxx.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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: link
Be 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).