From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: GDB 18.1 release update - 2026-09-14
Date: Mon, 14 Sep 2026 09:41:49 +0100 [thread overview]
Message-ID: <87h5jscjhu.fsf@redhat.com> (raw)
Hi everyone,
Quick update on the 18.1 release. You might have noticed the lack of
GDB 18 release! We still had a couple of issues unresolved, so the
release has been pushed back to :
Fri Sep 25 2026
Here is a quick recap of the changes since the last update:
Fixed Since the Previous Update:
--------------------------------
* gdb/34616 - Enums are mapped to wrong values
https://sourceware.org/bugzilla/show_bug.cgi?id=34616
This bug was introduced in GDB 17. A patch has been posted,
reviewed, and merged since the last release update, nice one! Commit
74dd30195333639d5d10607a0c666a357c04358c on the gdb-18-branch
resolved this issue.
Still Open Since Previous Update:
---------------------------------
* 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
This has been reviewed and needs a new version posting. I hear that
Andrew is currently working on this.
* gdb/34561 - Problem reading OS generated corefiles on systems with Intel AMX support
https://sourceware.org/bugzilla/show_bug.cgi?id=34561
Patches were posted here:
https://inbox.sourceware.org/gdb-patches/20260904100648.1705702-1-christina.joos@intel.com
Patch has been reviewed, hopefully a new version will be posted this week.
* gdb/34555 - gdb memory exhaustion on gdb.base/many-headers.exp
https://sourceware.org/bugzilla/show_bug.cgi?id=34555
This issue is considered NICE TO HAVE, and I'm not currently planning
to hold the release for it.
This issue effects Solaris, and has existed in GDB for a while if I
understand things correctly (i.e. many releases now).
There was a patch for this posted here:
https://inbox.sourceware.org/gdb-patches/ydda4qdga7h.fsf@CeBiTec.Uni-Bielefeld.DE
The request for this fix to be included in GDB 18 was made here:
https://inbox.sourceware.org/gdb-patches/yddo6e9fi8a.fsf@CeBiTec.Uni-Bielefeld.DE
Based on this email:
https://inbox.sourceware.org/gdb-patches/yddjyowf87m.fsf@CeBiTec.Uni-Bielefeld.DE
It's not clear if there will be another version of this patch.
Added Since the Last Update:
----------------------------
* Nothing.
Thanks,
Andrew
next reply other threads:[~2026-09-14 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 8:41 Andrew Burgess [this message]
2026-09-14 13:16 ` Simon Marchi
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=87h5jscjhu.fsf@redhat.com \
--to=aburgess@redhat.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