Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: GDB 15.1 release update (2024-03-23)
Date: Sat, 23 Mar 2024 08:17:39 +0400	[thread overview]
Message-ID: <Zf5X41FB6lOLZ5gU@adacore.com> (raw)

Hi everyone,

First, a reminder of our target dates:

  - Pre-release:    13-14 April 2024
  - Release (15.1): 27-28 April 2024

As we'll see in the recap below, things are moving forward, albeit
slowly, and we also have one (and maybe two) new issues which have
been reported. As a result, I'm starting to think that maybe
we won't make the dates above, which isn't a complete surprise
since we know those dates were a little on the optimistic side.
We'll see!

Meanwhile, below is a quick overview of where we stand in terms
of known issues. Thank you to everyone for creating PRs, as
this helps tremendously with tracking!

Please do let us know if there are other issues you think should be
fixed in GDB 15.

Here is the recap:

Fixed Since the Previous Update:
--------------------------------

  * [TomT/AndrewB]
    Revert "Pass GUILE down to subdirectories"
    https://sourceware.org/pipermail/gdb-patches/2024-January/205898.html

    Pushed: https://sourceware.org/pipermail/gdb-patches/2024-March/207487.html

Added Since the Last Update:
----------------------------

  * [<unassigned> TomT?] rust/31517
    Rust upstream GDB tests regressions with GDB 15 (regression)
    https://sourceware.org/bugzilla/show_bug.cgi?id=31517

    Reports a regression, but Tom said the change was intentional:
    https://sourceware.org/bugzilla/show_bug.cgi?id=30330

    Mentions a followup patch:
    https://sourceware.org/pipermail/gdb-patches/2024-March/207190.html

  * [<unassigned> Pedro?] tui/31522
    TUI misses highlight after run to main
    https://sourceware.org/bugzilla/show_bug.cgi?id=31522

    (opened 2023-03-21)

Other Ongoing Items:
--------------------

  * [<unassigned>] symtab/30520
    Slow lookup_symbol_in_objfile
    https://sourceware.org/bugzilla/show_bug.cgi?id=30520

        Feb patch series (v2, 2024-02-15):
        https://sourceware.org/pipermail/gdb-patches/2024-February/206442.html

        IIUC, needs some adjustments, and also waiting for copyright
        assignment papers to get through.

  * [TomT] symtab/30837
    [gdb/symtab, index-cache] data race on current_inferior
    https://sourceware.org/bugzilla/show_bug.cgi?id=30837

        Patch submitted in Feb, with rebase sent Mar 12th:
        [PATCH] Capture warnings when writing to the index cache
        https://sourceware.org/pipermail/gdb-patches/2024-March/207215.html

  * [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

  * [TomT] gdb/31264
    [gdb] ThreadSanitizer: data race format.c:132 in bfd_preserve_save
    https://sourceware.org/bugzilla/show_bug.cgi?id=31264

    Binutils patch series:
    - [PATCH 1/3] Make several more BFD globals thread-local
      https://sourceware.org/pipermail/binutils/2024-March/133102.html
      (still being worked on, last message 2024-03-19)
    - [PATCH 2/3] Do not call fputc from _bfd_doprnt
      https://sourceware.org/pipermail/binutils/2024-February/132411.html
      (approved by Nick)
    - [PATCH 3/3] Introduce bfd_print_error function
      https://sourceware.org/pipermail/binutils/2024-February/132412.html
      (approved by Nick)

  * [CarlEL] 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

  * [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...

Not Blocking, But Keep An Eye On:
---------------------------------

  < none >

-- 
Joel

             reply	other threads:[~2024-03-23  4:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23  4:17 Joel Brobecker [this message]
2024-03-23  5:22 ` Thiago Jung Bauermann
2024-03-26 15:48 ` Tom Tromey

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=Zf5X41FB6lOLZ5gU@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