From: Simon Marchi <simark@simark.ca>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: GDB 18.1 release update -- 2026-09-07
Date: Fri, 11 Sep 2026 09:15:47 -0400 [thread overview]
Message-ID: <e175e9c7-168e-42a5-9639-b076795c3ca8@simark.ca> (raw)
In-Reply-To: <87o6e9qk47.fsf@redhat.com>
On 2026-09-07 09:14, Andrew Burgess wrote:
>
> 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.
Hi Andrew,
There has been this user bug report a few days ago:
Enums are mapped to wrong values
https://sourceware.org/bugzilla/show_bug.cgi?id=34616
It is a regression introduced in GDB 17 (meaning there is already a
release with the bug), but I think it would be nice to have it fixed in
GDB 18, if we think the fix is not too risky. I sent a patch for it:
https://inbox.sourceware.org/gdb-patches/20260910022902.895931-1-simon.marchi@polymtl.ca/
Simon
next prev parent reply other threads:[~2026-09-11 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 13:14 Andrew Burgess
2026-09-11 13:15 ` Simon Marchi [this message]
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=e175e9c7-168e-42a5-9639-b076795c3ca8@simark.ca \
--to=simark@simark.ca \
--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