From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: simon.marchi@polymtl.ca, aburgess@redhat.com,
Joel Brobecker <brobecker@adacore.com>
Subject: Ready for GDB 11.2 release? ("re-spin") update (2021-12-11)
Date: Sat, 11 Dec 2021 12:02:04 +0400 [thread overview]
Message-ID: <YbRa/DVuelc47bm7@adacore.com> (raw)
Hi everyone,
One last issue left to fix. As we can see in the summary of
that issue below, we've already had a v2 patch since Nov 23rd.
One last review and confirmation whether it looks OK for a .2
or not?
As soon as the issue is fixed, I'll work on publishing the 11.2
the following weekend.
Thank you!
---
Fixed Since the Previous Update:
--------------------------------
* [Tromey] <PR rust/28637>
Allow DW_ATE_UTF for Rust characters
https://sourceware.org/bugzilla/show_bug.cgi?id=28637
* [BrunoL] <PR c++/28480>
Incorrect field ambiguity detection due to [[no_unique_address]]
https://sourceware.org/bugzilla/show_bug.cgi?id=28480
Added Since the Last Update:
----------------------------
< none :-) >
Other Ongoing Items:
--------------------
* [Andrew?] <PR gdb/28405>
arm-none-eabi: internal-error: first_resumed_thread != nullptr failed assertion
https://sourceware.org/bugzilla/show_bug.cgi?id=28405
v2 version of the patch (Nov 23):
https://sourceware.org/pipermail/gdb-patches/2021-November/183720.html
Waiting for review, ping sent on Dec 4th.
Not Critical, but Requested:
----------------------------
* [SimonM as awesome supporter and reviewer] <PR gdb/24069>
gdb on OSX Mojave hangs in darwin_decode_message
https://sourceware.org/bugzilla/show_bug.cgi?id=24069
Some movement on Nov 27th, after a period of no progress since
Jul 2021.
I know that the state of GDB on MacOS is very poor at the moment,
and so having this PR fixed for 11.1 would be very nice. I don't
think this PR should block the release, though. This is not new,
and I'm not sure whether we can expect for us to converge without
too much delay. There are good signs, though, with regular
activity on the PR, lately. So let's see how it goes...
* [BerndE] Improve debugging of optimized code
https://sourceware.org/pipermail/gdb-patches/2021-January/175617.html
This is reported to fix <PR c++/25987>
Wrong line for code containing inlined functions
Andrew xref-ed to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94474
(2021-09-05) v3 posted at:
[0/3] https://sourceware.org/pipermail/gdb-patches/2021-September/181829.html
[1/3] https://sourceware.org/pipermail/gdb-patches/2021-September/181830.html
[2/3] https://sourceware.org/pipermail/gdb-patches/2021-September/181831.html
[3/3] https://sourceware.org/pipermail/gdb-patches/2021-September/181832.html
Looks like those patches are a challenge to review
https://sourceware.org/pipermail/gdb-patches/2021-September/181930.html
* [Simon] <PR gdb/26868>
Follow-up on x86-64 stub submission
https://sourceware.org/bugzilla/show_bug.cgi?id=26868
This is the submission in question:
https://sourceware.org/pipermail/gdb-patches/2020-November/173182.html
For me, although I am not a lawyer, I don't think we can accept
the contribution without the author signing a copyright assignment
form.
* [PhilippeW] Fix/complete option list/description in manual and in gdb --help
RFA v2 (2021-06-20):
[RFAV2] Fix/complete option list/description in manual and in gdb --help.
https://sourceware.org/pipermail/gdb-patches/2021-June/180186.html
--
Joel
reply other threads:[~2021-12-11 8:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YbRa/DVuelc47bm7@adacore.com \
--to=brobecker@adacore.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).