Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Tom de Vries <tdevries@suse.de>, Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: ready for the GDB 17.2 corrective release?
Date: Tue, 21 Apr 2026 10:23:00 +0100	[thread overview]
Message-ID: <87ik9k3bwr.fsf@redhat.com> (raw)
In-Reply-To: <12ebfa51-ca19-4542-9b85-18caae3a695f@suse.de>

Tom de Vries <tdevries@suse.de> writes:

> On 4/20/26 8:32 PM, Joel Brobecker wrote:
>> Hi Tom,
>> 
>>> I'd like to nominate PR31449 [1] and PR33794 [2].  They're both crashes that
>>> happen when querying the user about enabling debuginfod while enabling TUI.
>>>
>>> I've submitted low-risk patches for both PRs (
>>> https://sourceware.org/pipermail/gdb-patches/2026-April/226551.html ).
>>>
>>> I'm not sure if the PRs are severe enough to block the release for: crashes
>>> are serious, but the likelihood that such a crash will trigger is not high,
>>> I think, which is probably why we have lived with it, probably since the
>>> query was introduced in 2021.
>>>
>>> But the fact that low-risk patches are available might be reason enough to
>>> consider including them.
>> 
>> Thanks for pointing those two PRs out. Let's start by marking them as
>> targetting 17.2 for the time being, so we don't forget about them.
>> 
>> How soon do you anticipate you'll be able to have those changes pushed?
>
> Well, they're waiting for review.

I'll try to look at these either today, or Thu/Fri this week.  If
someone else wants to look first, then feel free :)

Thanks,
Andrew


      reply	other threads:[~2026-04-21  9:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-19 13:57 Joel Brobecker
2026-04-20  7:23 ` Tom de Vries
2026-04-20 18:32   ` Joel Brobecker
2026-04-20 18:50     ` Tom de Vries
2026-04-21  9:23       ` Andrew Burgess [this message]

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=87ik9k3bwr.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --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