From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: GDB 13 release -- 2023-01-07 update
Date: Sat, 7 Jan 2023 15:43:51 +0400 [thread overview]
Message-ID: <Y7la9/18qByiY1Qz@adacore.com> (raw)
Hello everyone,
Happy New Year!
Quick update: I think we might be very close to being able to produce
our first pre-release. We have one blocking PR, and the associated
patches just got approved. So my hope is to be able to publish
the first pre-release next weekend.
Fixed Since the Previous Update:
--------------------------------
* [Simon/TomDV] gdb/28224
Use-after-free when calling a GNU ifunc
https://sourceware.org/bugzilla/show_bug.cgi?id=28224
Not 100% sure that this is actually fixed because
the PR is still open, but IIUC it was fixed via
https://sourceware.org/bugzilla/show_bug.cgi?id=29941
Added Since the Last Update:
----------------------------
<none>
Other Ongoing Items:
--------------------
* [TomT] c++/29896
GDB git doesn't recognize template function name
https://sourceware.org/bugzilla/show_bug.cgi?id=29896
Patch series posted at this location (2022-12-15):
https://sourceware.org/pipermail/gdb-patches/2022-December/194795.html
Approved 2023-01-07.
* [Torbjorn] tdep/29738
Arm M-profile dwarf2 unwinder performance suffers from exponential growth
https://sourceware.org/bugzilla/show_bug.cgi?id=29738
patch v2, 2022-11-18, reviewed 2022-11-21:
https://sourceware.org/pipermail/gdb-patches/2022-November/193960.html
Aside from an email on Dec 8th, I don't see any updates on this one.
--
Joel
next reply other threads:[~2023-01-07 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 11:43 Joel Brobecker [this message]
2023-01-09 6:47 ` Torbjorn SVENSSON
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=Y7la9/18qByiY1Qz@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).