Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Joos, Christina" <christina.joos@intel.com>
To: Andrew Burgess <aburgess@redhat.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: GDB 18.1 release update -- 2026-08-14
Date: Mon, 24 Aug 2026 12:24:24 +0000	[thread overview]
Message-ID: <SN7PR11MB76386CE1AE64D3271F697E2D89A02@SN7PR11MB7638.namprd11.prod.outlook.com> (raw)
In-Reply-To: <877bls4t5f.fsf@redhat.com>

> -----Original Message-----
> From: Andrew Burgess <aburgess@redhat.com>
> Sent: Freitag, 14. August 2026 17:30
> To: gdb-patches@sourceware.org
> Subject: GDB 18.1 release update -- 2026-08-14
> 
> 
> 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?

Hi Andrew, 

I just entered this issue, which I think would be good to fix for GDB 18 release:
https://sourceware.org/bugzilla/show_bug.cgi?id=34561

Sorry for my late feedback on this, I have not been able to work last week.

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.

      parent reply	other threads:[~2026-08-24 12:24 UTC|newest]

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

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=SN7PR11MB76386CE1AE64D3271F697E2D89A02@SN7PR11MB7638.namprd11.prod.outlook.com \
    --to=christina.joos@intel.com \
    --cc=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