From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: luis.machado@linaro.org, ssbssa@yahoo.de, tdevries@suse.de,
simon.marchi@polymtl.ca, tankut.baris.aktemur@intel.com,
bernd.edlinger@hotmail.de, philippe.waroquiers@skynet.be,
Joel Brobecker <brobecker@adacore.com>
Subject: GDB 11.1 release prep update (2021-07-24)
Date: Sat, 24 Jul 2021 14:19:14 -0700 [thread overview]
Message-ID: <20210724211914.GA2299597@adacore.com> (raw)
Hello everyone,
Here is an update of where things stand, regarding the 11.1 release.
The good news is that we've made progress (including progress with
fixes that were not tracked here). The bad news is that some items
are simply not showing any visible sign of progress or even activity.
Let's see how it goes for this week; if necessary, I might start
suggesting alternative options next week (sounds ominous, but one
of those options will be to continue waiting)...
Thank you!
---
Fixed Since the Previous Update:
--------------------------------
* [TomT] <PR gdb/28093>
set language unknown -> print "foo" -> GDB crash
https://sourceware.org/bugzilla/show_bug.cgi?id=28093
Added Since the Last Update:
----------------------------
< none >
Other Ongoing Items:
--------------------
* [LuisM] <PR corefiles/27909>
AArch64 MTE fixes and corefile support
https://sourceware.org/bugzilla/show_bug.cgi?id=27909
Status 2021-07-11:
- 3 patches already approved
- 1 patch waiting for review on non-AArch64 part:
https://sourceware.org/pipermail/gdb-patches/2021-July/180537.html
* [HannesD] some Python-suport changes for the TUI interface
I'm getting concerned about this one, as there is currently
little activity on them.
[PATCHv2 1/2] Implement locals TUI window
https://sourceware.org/pipermail/gdb-patches/2021-June/179539.html
(I think this patch should provide more information in the commit
message about what its goal is)
[PATCHv2 2/2] Use method children instead of to_string in pretty printers
https://sourceware.org/pipermail/gdb-patches/2021-June/179540.html
(same suggestion)
2021-07-17: JoelB did a review, and had one comment.
* [TomDV/Simon] <PR gdb/28004>
DW_AT_ranges with form DW_FORM_sec_offset problem
https://sourceware.org/bugzilla/show_bug.cgi?id=28004
Not a blocker for branching, but should be fixed before the release.
Last movement I see on this ticket is from a month ago :-(.
* [Tankut] <PR mi/28076> (reported by Jonah G)
[regression] Cannot remove condition from breakpoint from M
https://sourceware.org/bugzilla/show_bug.cgi?id=28076
Patch at: https://sourceware.org/pipermail/gdb-patches/2021-July/180818.html
Code approved, just waiting for doc approval.
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
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
(2021-05-31) v2 posted at:
[0/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179367.html
[1/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179368.html
[2/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179370.html
[3/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179369.html
Patch submitted at:
https://sourceware.org/pipermail/gdb-patches/2020-September/172083.html
(May 24th) High-level pre-review done at:
https://sourceware.org/pipermail/gdb-patches/2021-May/179191.html
No movement since then. Not blocking for branching since it would
be safe to backport after branching. Not blocking for release either.
* [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
next reply other threads:[~2021-07-24 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 21:19 Joel Brobecker [this message]
2021-07-26 6:52 ` Aktemur, Tankut Baris
2021-07-31 10:59 ` Philippe Waroquiers
2021-08-01 23:19 ` 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=20210724211914.GA2299597@adacore.com \
--to=brobecker@adacore.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@linaro.org \
--cc=philippe.waroquiers@skynet.be \
--cc=simon.marchi@polymtl.ca \
--cc=ssbssa@yahoo.de \
--cc=tankut.baris.aktemur@intel.com \
--cc=tdevries@suse.de \
/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).