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-08-14
Date: Fri, 14 Aug 2026 16:29:48 +0100	[thread overview]
Message-ID: <877bls4t5f.fsf@redhat.com> (raw)


Hi,

Quick update on the 18.1 release.

The release is still currently scheduled for:

  09-Sep-2026

There are currently two open bugs in bugzilla tagged with 18.1 target
milestone:

  * PR gdb/33205
    [gdb/testsuite, meta] Minimum supported tcl version
    https://sourceware.org/bugzilla/show_bug.cgi?id=33205

    This bug is assigned to Tom Tromey, it looks like some patches were
    committed, but also there is possibly a still open question in the
    bug chat.

    Can this bug be closed?

    It seems related to GDB's testsuite infrastructure.  Does this
    really need to be a blocker for 18.1?  Or could we clear the target
    milestone here?

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

    This bug is also assigned to Tom Tromey, and is a regression
    introduced since gdb-17-branch by commit
    c879f4dc3e317cf6353a45a803ecf00d577a13d8.

    There is some discussion in the bug thread which I haven't tried to
    understand yet, but there have been no commits.

    Given this is a regression since the last release it would be nice
    if this could be resolved before release.

Are there any other issues that people think need resolving before we
release?

Thanks,
Andrew


             reply	other threads:[~2026-08-14 15:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 15:29 Andrew Burgess [this message]
2026-08-14 15:48 ` Rainer Orth
2026-08-24 12:24 ` Joos, Christina

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=877bls4t5f.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