From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: GDB 13.2 (corrective) release -- 2023-05-05 Update
Date: Sun, 7 May 2023 18:19:30 -0700 [thread overview]
Message-ID: <ZFhOIjRsUsIpczjU@adacore.com> (raw)
Hi Everyone,
No real change since our last update a week ago: So far, no known
blocking issue that we want to fix before we publish GDB 13.2.
=> Target release date: Sat 27 May 2023.
Please let us know if there are issues that we should consider for
that release.
FTR: List of fixes in GDB 13.2 as of now:
-----------------------------------------
* PR testsuite/30158 (rustc testsuite fails with 13.1, apparently worked before with trunk 20230114 on i686-linux-gnu and powerpc64le-linux-gnu)
* PR gdb/30214 (GDB 13.1 does not compile on FreeBSD 13.1)
* PR gdb/30240 ((linux/aarch) thread.c:86: internal-error: inferior_thread: Assertion `current_thread_ != nullptr' failed)
* PR symtab/30357 (Segmentation fault for the 'start' command)
* PR symtab/30369 ([gdb/symtab] False match issue in skip_prologue_using_linetable)
* PR gdb/30423 (Build failures with clang 16)
--
Joel
next reply other threads:[~2023-05-08 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 1:19 Joel Brobecker [this message]
2023-05-11 22:19 ` Tom Tromey
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=ZFhOIjRsUsIpczjU@adacore.com \
--to=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).