GDB 18.1 release update -- 2026-09-01

GDB 18.1 release update -- 2026-09-01

[Andrew Burgess]

Hi everyone,

Quick update on the 18.1 release.  Release is still currently scheduled
for:

    Fri Sep 11 2026

Here is a quick recap of the changes since the last update:

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

 * gdb/34195 - Windows tests report "No unwaited-for children left."
   https://sourceware.org/bugzilla/show_bug.cgi?id=34195

   A patch for this issue has been merged as commit 524f668fa5aede1a on
   gdb-18-branch.

Still Open Since Previous Update:
---------------------------------

 * dap/34548 - gdb.dap/pause.exp hangs on Solaris
   https://sourceware.org/bugzilla/show_bug.cgi?id=34548

   A V2 patch was posted here:

   https://inbox.sourceware.org/gdb-patches/ydd4iged3z5.fsf_-_@CeBiTec.Uni-Bielefeld.DE

 * gdb/33447 - Can't find class methods on clang compiled libraries
   https://sourceware.org/bugzilla/show_bug.cgi?id=33447

   A V3 patch was posted for this here:

   https://inbox.sourceware.org/gdb-patches/897f5eb957bdfd90cd3fd5efa662021ed5c2aef2.1788269262.git.aburgess@redhat.com

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

 * gdb/34561 - Problem reading OS generated corefiles on systems with Intel AMX support
   https://sourceware.org/bugzilla/show_bug.cgi?id=34561

   This might be fixed by the patches here:

   https://inbox.sourceware.org/gdb-patches/20250911072711.1211004-1-vigbalas@amd.com/

   But there's also discussion of a simpler fix, which might be better
   for the GDB 18 release only:

   https://sourceware.org/bugzilla/show_bug.cgi?id=34561#c2

   I'm a little unclear what the plan is for this issue right now.
   

Thanks,
Andrew

Re: GDB 18.1 release update -- 2026-09-01

[Tom Tromey]

>>>>> "Andrew" == Andrew Burgess <aburgess@redhat.com> writes:

Andrew> Added Since the Last Update:
Andrew> ----------------------------

I've added another one:

    https://sourceware.org/bugzilla/show_bug.cgi?id=34583

This is a regression, though I suppose it's somewhat obscure, as it only
affects "attach" to an x86 (not x86_64) program on Windows when using
gdbserver.

If you'd rather reset the target milestone and ignore this one for the
release, I wouldn't object.

I've bisected this and I'm researching a fix.

Tom

Re: GDB 18.1 release update -- 2026-09-01

[Andrew Burgess]

Tom Tromey <tromey@adacore.com> writes:

>>>>>> "Andrew" == Andrew Burgess <aburgess@redhat.com> writes:
>
> Andrew> Added Since the Last Update:
> Andrew> ----------------------------
>
> I've added another one:
>
>     https://sourceware.org/bugzilla/show_bug.cgi?id=34583
>
> This is a regression, though I suppose it's somewhat obscure, as it only
> affects "attach" to an x86 (not x86_64) program on Windows when using
> gdbserver.
>
> If you'd rather reset the target milestone and ignore this one for the
> release, I wouldn't object.
>
> I've bisected this and I'm researching a fix.

I'm happy to wait and see how easily fixable this might be first.

Thanks for working on this.

Thanks,
Andrew

RE: GDB 18.1 release update -- 2026-09-01

[Joos, Christina]

> Added Since the Last Update:
> ----------------------------
> 
>  * gdb/34561 - Problem reading OS generated corefiles on systems with Intel
> AMX support
>    https://sourceware.org/bugzilla/show_bug.cgi?id=34561
> 
>    This might be fixed by the patches here:
> 
>    https://inbox.sourceware.org/gdb-patches/20250911072711.1211004-1-
> vigbalas@amd.com/
> 
>    But there's also discussion of a simpler fix, which might be better
>    for the GDB 18 release only:
> 
>    https://sourceware.org/bugzilla/show_bug.cgi?id=34561#c2
> 
>    I'm a little unclear what the plan is for this issue right now.

Hi Andrew, 

I am working on this and will post a patch soon based on the simple fix I indicated in the comments.

There is one unrelated side issue I ran into, which is the reason I did not post it so far.

Christina 

________________________________________
Intel Deutschland GmbH 

Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany 

Tel: +49 (89) 99143-0 

www.intel.de 

Managing Directors: Candice Moore, Jeffrey Schneiderman, Ramachandran Sitaraman

Chairperson of the Supervisory Board: Sonja Pierer

Registered Seat: Munich Commercial Register B: Amtsgericht Munich HRB 186928

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

RE: GDB 18.1 release update -- 2026-09-01

[Andrew Burgess]

"Joos, Christina" <christina.joos@intel.com> writes:

>> Added Since the Last Update:
>> ----------------------------
>> 
>>  * gdb/34561 - Problem reading OS generated corefiles on systems with Intel
>> AMX support
>>    https://sourceware.org/bugzilla/show_bug.cgi?id=34561
>> 
>>    This might be fixed by the patches here:
>> 
>>    https://inbox.sourceware.org/gdb-patches/20250911072711.1211004-1-
>> vigbalas@amd.com/
>> 
>>    But there's also discussion of a simpler fix, which might be better
>>    for the GDB 18 release only:
>> 
>>    https://sourceware.org/bugzilla/show_bug.cgi?id=34561#c2
>> 
>>    I'm a little unclear what the plan is for this issue right now.
>
> Hi Andrew, 
>
> I am working on this and will post a patch soon based on the simple fix I indicated in the comments.
>
> There is one unrelated side issue I ran into, which is the reason I did not post it so far.

That's awesome.  Thanks for the update.

Thanks,
Andrew

Re: GDB 18.1 release update -- 2026-09-01

[Rainer Orth]

Hi Andrew,

> Still Open Since Previous Update:
> ---------------------------------
>
>  * dap/34548 - gdb.dap/pause.exp hangs on Solaris
>    https://sourceware.org/bugzilla/show_bug.cgi?id=34548
>
>    A V2 patch was posted here:
>
>    https://inbox.sourceware.org/gdb-patches/ydd4iged3z5.fsf_-_@CeBiTec.Uni-Bielefeld.DE

the patch (or rather the minor revision at

     https://sourceware.org/pipermail/gdb-patches/2026-September/230000.html

) has now been committed to trunk.

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

There's also

  * corefiles/34555
    https://sourceware.org/bugzilla/show_bug.cgi?id=34555

    A patch has been posted, but not reviewed yet:

    https://sourceware.org/pipermail/gdb-patches/2026-August/229698.html

Thanks.
	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

Re: GDB 18.1 release update -- 2026-09-01

[Andrew Burgess]

Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:

> Hi Andrew,
>
>> Still Open Since Previous Update:
>> ---------------------------------
>>
>>  * dap/34548 - gdb.dap/pause.exp hangs on Solaris
>>    https://sourceware.org/bugzilla/show_bug.cgi?id=34548
>>
>>    A V2 patch was posted here:
>>
>>    https://inbox.sourceware.org/gdb-patches/ydd4iged3z5.fsf_-_@CeBiTec.Uni-Bielefeld.DE
>
> the patch (or rather the minor revision at
>
>      https://sourceware.org/pipermail/gdb-patches/2026-September/230000.html
>
> ) has now been committed to trunk.
>
>> Added Since the Last Update:
>> ----------------------------
>
> There's also
>
>   * corefiles/34555
>     https://sourceware.org/bugzilla/show_bug.cgi?id=34555
>
>     A patch has been posted, but not reviewed yet:
>
>     https://sourceware.org/pipermail/gdb-patches/2026-August/229698.html

I happy to track this bug for GDB 18, and I'll try to review this patch
next.  But... if I understand this bug report correctly, this is a long
standing bug in GDB, not a regression introduced in the last couple of
releases.  As such I'd prefer that we didn't hold the release for this
fix (which I will review next, so might be fixed anyway).

I'd really like to avoid holding the release for:

  + new features,
  + fixes for things that have never worked, or
  + fixes for things that have been broken for 2+ releases.

I'm about to send out another 'release update' and I plan to list this
bug under "nice to have".  Then I'll go and review the fix, so hopefully
we'll land this anyway.

I know that might not be the answer you were hoping for, but I will make
reviewing that patch a priority.

Thanks,
Andrew