public inbox for gdb-patches@sourceware.org
 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-05-03)
Date: Fri, 3 May 2024 18:26:31 -0700	[thread overview]
Message-ID: <ZjWOx+IQITp72TrB@adacore.com> (raw)

Hi everyone,

Another quick update on the status of the release. Thiago's super
helpful update inspired me to look at the current situation again;
thanks Thiago!

We have a new entrant this week with a use-after-free issue.
Not sure yet if someone has said they are looking at it or not.
I'll keep an eye on it.

Some very good progress in the past week otherwise, so unless the new
use-after-free issue takes a lot of time to fix, I am thinking we're
getting close to branching and pre-release!

As mentioned before, at this stage, we will want to create the branch
and then pre-release + release as soon as all identified issues below
are fixed. More precisely:

  - Pre-release: As soon as all blocking issues are solved.
  - Release (15.1): Two weeks after pre-release.

Thanks everyone!

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

  * [CarlEL/ThiagoB] testsuite/31312
    attach-many-short-lived-threads gives inconsistent results (POWER 10)
    https://sourceware.org/bugzilla/show_bug.cgi?id=31312

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

  * [<???>] symtab/31694
    heap-use-after-free in index-cache
    https://sourceware.org/bugzilla/show_bug.cgi?id=31694

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, there is an agreement between author and reviewer about
        the (small) required changes. But copyright assignment papers
        are still waiting to be signed.  (no change since Feb 15)

  * [TomT] gdb/31261
    [gdb] ThreadSanitizer: data race objfiles.c:648 in objfile_relocate1
    https://sourceware.org/bugzilla/show_bug.cgi?id=31261

        Patch series v2 (2024-04-16):
        https://sourceware.org/pipermail/gdb-patches/2024-April/208159.html

        Simpler series. Awaiting comments, but will otherwise check
        the series in if not.

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

  * [Thiago]
    various improvements to aarch64 MOPS (Memory Operations)
    https://sourceware.org/bugzilla/show_bug.cgi?id=31666

    v1 patch series (2024-05-03):
    https://sourceware.org/pipermail/gdb-patches/2024-May/208822.html

-- 
Joel

                 reply	other threads:[~2024-05-04  1:26 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=ZjWOx+IQITp72TrB@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).