Re: ready for the GDB 17.2 corrective release?

[Tom de Vries <tdevries@suse.de>]

On 4/19/26 3:57 PM, Joel Brobecker wrote:
> Hi everyone,
> 
> It's been 4 months since we released GDB 17.1, so time to publish
> a corrective release. So far, we have 12 confirmed fixes, with
> a 13th one where I suspect the fix is in and we just forgot to close
> the PR.
> 
> As of now, I propose the following release date for 17.2:
> 
>          Sat-Sun May 02-03
> 
> Are there any other issues that we know of that we have identified
> as must-fix for 17.2?  Please let us know if you think there are blocking
> items, as otherwise the date above is when I intend to publish the next
> release.

Hi Joel,

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,
- Tom

> 
> Thank you!
> 

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=31449
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=33794