From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: GDB 17.2 release update -- 2026-04-25
Date: Sat, 25 Apr 2026 12:10:38 -0700 [thread overview]
Message-ID: <ae0RrhlVXxhOv7fx@adacore.com> (raw)
Hi everyone,
Quick update on the 17.2 release, where the target date is next weekend:
Sat-Sun May 02-03
As of now, we have 2 PRs left to fix in our TODO list, normally
in good hands. Please let us know if there are some other last-minute
issues you think we should include in the 17.2 corrective release.
Otherwise, as soon as the two PRs are fixed, I plan to publish
the 17.2 release the first weekend that follows the fix.
Here is a quick recap of the changes since last week:
Fixed Since the Previous Update:
--------------------------------
* [Thiago] build/33747
Incompatible with MUSL libc: no member named 'c_ospeed' in 'termios'
https://sourceware.org/bugzilla/show_bug.cgi?id=33747
Added Since the Last Update:
----------------------------
* [TomDV] tui/31449
TUI crash with debuginfod support
https://sourceware.org/bugzilla/show_bug.cgi?id=31449
https://sourceware.org/pipermail/gdb-patches/2026-April/226551.html
* [TomDV] tui/33794
[gdb/tui] Recursive readline use
https://sourceware.org/bugzilla/show_bug.cgi?id=33794
Other Ongoing Items:
--------------------
< none :) >
Not Blocking, But Keep An Eye On:
---------------------------------
< none :) >
Thank you all!
--
Joel
next reply other threads:[~2026-04-25 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 19:10 Joel Brobecker [this message]
2026-05-08 9:37 ` Andrew Burgess
2026-05-08 14:16 ` Joel Brobecker
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=ae0RrhlVXxhOv7fx@adacore.com \
--to=brobecker@adacore.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