Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Brandon Belew <brandon.belew@zetier.com>
To: brobecker@adacore.com (Joel Brobecker)
Cc: gdb-patches@sourceware.org, aburgess@redhat.com
Subject: Re: GDB 16.3 release - 2025-03-01 update
Date: Mon, 03 Mar 2025 10:08:32 -0500	[thread overview]
Message-ID: <hwjgya1pvexibz.fsf@brandonb.zetier.com> (raw)
In-Reply-To: <Z8LgB5JWwqO9i/u0@adacore.com> (Joel Brobecker's message of "Sat,  1 Mar 2025 14:23:03 +0400")

brobecker@adacore.com (Joel Brobecker) writes:

> Quick update on the GDB 16.3 release, normally scheduled around 3 months
> after the corresponding .1 which was released Jan 18, therefore:
>
>   - Target Release Date: Apr 19-20.
>
> So far, we have two fixes in the gdb-16-branch since we release 16.2
> (see below). No additional issues currently listed in bugzilla as
> targeting the 16.3 release.
>
> If you know of issues that we should aim to fix before we publish
> the 16.3 release, please create a PR, set the "Target Milestone"
> to 16.3, with a note explaining the rationale.

Hi, I'm a new contributor and I don't have permissions to modify the
Target Milestone on the bug I reported in bugzilla, but bug 32441 [1]
has an attached patch that was just approved by Andrew Burgess; see
Message ID <87ikouz5ys.fsf@redhat.com> [2]. This fixes a segfault in
core file generation, much like the other corefiles/32634 fix already
being included in the 16.3 release. I would love to see this fix
included!

Thanks!
    ~Brandon


[1] https://sourceware.org/bugzilla/show_bug.cgi?id=32441
[2] https://sourceware.org/pipermail/gdb-patches/2025-February/215909.html

  parent reply	other threads:[~2025-03-03 15:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-01 10:23 Joel Brobecker
2025-03-03 14:23 ` Luis Machado
2025-03-04  3:07   ` Joel Brobecker
2025-03-03 15:08 ` Brandon Belew [this message]
2025-03-04  3:12   ` Joel Brobecker
2025-03-07 14:07     ` Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2024-12-20 22:17 [PATCH] [PR corefiles/32441] Fix segfault if target_fileio_read_alloc fails brandon.belew
2025-01-16 10:27 ` Luis Machado
2025-01-16 16:28   ` Brandon Belew
2025-01-16 16:51 ` Andrew Burgess
2025-01-16 17:36   ` Brandon Belew
2025-01-20 14:44     ` Andrew Burgess
2025-01-27 20:20   ` [PATCH v2] " Brandon Belew
2025-02-18 23:44     ` Brandon Belew
2025-02-28 11:03     ` Andrew Burgess
2025-03-04 13:47       ` [PATCH v3] " Brandon Belew
2025-03-09  4:17       ` [PATCH v2] " 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=hwjgya1pvexibz.fsf@brandonb.zetier.com \
    --to=brandon.belew@zetier.com \
    --cc=aburgess@redhat.com \
    --cc=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