From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: GDB 15.1 release update (2024-04-14)
Date: Sun, 14 Apr 2024 11:15:35 -0700 [thread overview]
Message-ID: <ZhwdR93hp5QTBs02@adacore.com> (raw)
Hi everyone,
Below is a quick overview of where we stand in terms of known issues.
One new item got added to the list but I have good confidence this
new one will be resolved soon (v5 patch series is out, and one contributor
thought it looked good).
On the 4 remaining issues that we identified as blocking, I may have
missed some messages, but so far as I can tell, I did not see any update
on them. For those which have been without update the longest, I've
sent a small request for an update.
At this state the schedule is follow:
- Pre-release: As soon as all blocking issues are solved.
- Release (15.1): Two weeks after pre-release.
As always, please let us know if there are other issues we should
fix before releasing.
Fixed Since the Previous Update:
--------------------------------
< none >
Added Since the Last Update:
----------------------------
* [TomDV] symtab/31268
gdb.base/unwind-on-each-insn-amd64.exp regression
https://sourceware.org/bugzilla/show_bug.cgi?id=31268
v5 patch series here (2024-04-09):
https://sourceware.org/pipermail/gdb-patches/2024-April/207959.html
Other Ongoing Items:
--------------------
* [<unassigned>] symtab/30520
Slow lookup_symbol_in_objfile
https://sourceware.org/bugzilla/show_bug.cgi?id=30520
(no change since Feb 15)
Feb patch series (v2, 2024-02-15):
https://sourceware.org/pipermail/gdb-patches/2024-February/206442.html
IIUC, there is an agreement between author and reviewer about
the (small) required changes. But copyright assignment papers
are still waiting to be signed.
* [TomT] gdb/31261
[gdb] ThreadSanitizer: data race objfiles.c:648 in objfile_relocate1
https://sourceware.org/bugzilla/show_bug.cgi?id=31261
Fix race in DWARF reader (2024-02-17):
https://sourceware.org/pipermail/gdb-patches/2024-February/206633.html
(Tom sent another email 2024-04-03 sharing more of his thoughts,
and also saying he's appreciate insights if we have some)
* [TomT] gdb/31264
[gdb] ThreadSanitizer: data race format.c:132 in bfd_preserve_save
https://sourceware.org/bugzilla/show_bug.cgi?id=31264
New binutils patch series (2024-03-24):
https://sourceware.org/pipermail/binutils/2024-March/133155.html
* [CarlEL/ThiagoB] testsuite/31312
attach-many-short-lived-threads gives inconsistent results (POWER 10)
https://sourceware.org/bugzilla/show_bug.cgi?id=31312
Looked like the discussions have reached a consensus of accepting
this failure (2024-03-09), but there was a second questin that
wasn't wasn't understood yet, so Carl tried to dig deeper.
Meanwhile, Thiago indicated he's seeing the same kind of behavior
on AArch64 Linux (sometimes), and now has some leads he is
pursuing (go Thiago!)
Thiago posted a patch series that fixes the problem, but
with one known regression he hasn't had time to investigate:
https://sourceware.org/pipermail/gdb-patches/2024-March/207467.html
Pedro suggested an alternative approach to fix the problem,
which Thiago tried, but unfortunately created another issue.
To be investigated further.
Not Blocking, But Keep An Eye On:
---------------------------------
* [TomT and/or SimonM] gdb/31331
Wenum-constexpr-conversion should be fixed, soon treated as a hard error
https://sourceware.org/bugzilla/show_bug.cgi?id=31331
Last update was 2024-02-13.
Marked as targeting 15.1, but not sure this one is blocking
for 15.1...
* [Thiago]
various improvements to aarch64 MOPS (Memory Operations)
Related to this enhancement, there is a gdb/testsuite PR
to add watchpoint tests for those:
https://sourceware.org/bugzilla/show_bug.cgi?id=31484
--
Joel
next reply other threads:[~2024-04-14 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 18:15 Joel Brobecker [this message]
2024-04-19 20:37 ` Tom Tromey
2024-04-20 18:35 ` 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=ZhwdR93hp5QTBs02@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).