From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: GDB 13.2 (corrective) release -- 2023-05-14 Update
Date: Sun, 14 May 2023 17:50:50 -0700 [thread overview]
Message-ID: <ZGGB6uaTpnsf+zjg@adacore.com> (raw)
Hi everyone,
Compared to last week, one new PR got suggested for inclusion in
GDB 13.2 (thanks Tom). The fix should land pretty soon, so the current
target date for the GDB 13.2 release remains unchanged for now:
=> Target release date: Sat 27 May 2023.
Please let us know if there are issues that we should consider for
that release.
Fixed Since the Previous Update:
--------------------------------
< none >
Added Since the Last Update:
----------------------------
* [TomT] exp/30271
Addresses of static thread_local fields are badly calculated sometimes
https://sourceware.org/bugzilla/show_bug.cgi?id=30271
Other Ongoing Items:
--------------------
< none >
Not Blocking, But Keep An Eye On:
---------------------------------
< none >
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-15 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 0:50 Joel Brobecker [this message]
2023-05-16 16:49 ` Tom Tromey
2023-05-16 17:44 ` 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=ZGGB6uaTpnsf+zjg@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).