Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: GDB 18.1 release update -- 2026-09-07
Date: Mon, 07 Sep 2026 14:14:16 +0100	[thread overview]
Message-ID: <87o6e9qk47.fsf@redhat.com> (raw)


Hi everyone,

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

    Fri Sep 11 2026

We appear to be moving in the right direction.

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

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

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

   Commit 12e6c963f1e7ef331527d6992de19177a4eb9add on 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 is by far the biggest risk.  This was a regression since GDB 17,
   so could ideally do with being fixed.  This needs a review by someone
   familiar with GDB's DWARF handling.

 * 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

   I reviewed patch #1 with some thoughts, hopefully we can get this
   issue wrapped up and merged over the next couple of days.

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

 * 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

Thanks,
Andrew


             reply	other threads:[~2026-09-07 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 13:14 Andrew Burgess [this message]
2026-09-11 13:15 ` Simon Marchi
2026-09-12  1:40   ` 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=87o6e9qk47.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