GDB 17 Brings Hardware Shadow-Stack Debugging and AArch64 Guarded Control Stacks as the 17.2 Maintenance Release Lands
The GNU Debugger's 17 series adds support for debugging CET shadow stacks and AArch64 Guarded Control Stacks, with version 17.2 shipping in May 2026 as the current release.
Overview
The GNU Debugger, the decades-old command-line debugger at the foundation of much of the open-source toolchain, has reached its 17 series. The current release, GDB 17.2, shipped on May 10, 2026 as a maintenance update, according to the GDB project’s news page. It builds on GDB 17.1, released December 20, 2025, which introduced the series’ substantive new capabilities, per the GDB 17.1 release announcement.
The headline additions in the 17 series center on debugging the hardware control-flow-integrity features that modern processors have begun enforcing: Intel and AMD shadow stacks on x86-64, and the equivalent Guarded Control Stacks on AArch64. The release also extends GDB’s Debugger Adapter Protocol support, a sign of the debugger’s continued adaptation to editor-based workflows.
GDB is a source-level debugger for Ada, C, C++, Fortran, Go, Rust, and many other languages, as the release announcement describes it. First written by Richard Stallman in 1986 as part of the GNU system and distributed under the GNU General Public License, it remains the reference debugger for native code on Unix-like systems, according to Wikipedia.
What We Know
Debugging hardware control-flow protections
The most consequential additions in GDB 17 target processor security features. The release adds x86-64 CET shadow stack support, according to the GDB 17.1 announcement. Control-flow Enforcement Technology is the Intel and AMD mechanism that maintains a protected shadow copy of return addresses to detect return-oriented-programming attacks; debugging a program that uses it previously meant the debugger had to understand that parallel stack.
On the Arm side, GDB 17 can now debug Linux programs that use AArch64 Guarded Control Stacks, the announcement states. Guarded Control Stacks are Arm’s analogous return-address-protection feature. The Linux news site LWN likewise highlighted CET shadow stack support and Guarded Control Stacks debugging as among the release’s major additions.
Recording, threads, and architecture support
The release expands GDB’s reverse-debugging “record” feature to the RISC-V rv64gc architecture, according to the announcement. The info threads command gained two new options, -stopped and -running, to limit the list of displayed threads, the announcement notes. On Linux and FreeBSD, the addresses shown by the info sharedlibrary command are now for the full memory range allocated to the shared library.
GDB 17 also adds built-in support for thread-local storage on Linux as a fallback, supported on the x86_64, aarch64, ppc64, s390x, and riscv architectures when compiled with GLIBC or MUSL, per the announcement. A new command, set riscv numeric-register-names, displays RISC-V registers using their numeric names, and the Alpha target now supports target descriptions.
Editor integration and a quality-of-life touch
GDB’s Debugger Adapter Protocol implementation now supports the completions request, according to the announcement. The Debugger Adapter Protocol is the interface that lets editors and IDEs drive a debugger through a common wire format, and completion support brings GDB’s DAP front-end closer to the experience of a graphical debugger.
In a more visible change, warnings and error messages now start with an emoji — a warning sign or cross mark — if supported by the host charset, the announcement states. LWN noted the feature is configurable.
Deprecations and the 17.2 follow-up
The 17 series tightens its requirements. Support for Python versions older than 3.4 has been removed, and support for the stabs debugging format and the a.out/dbx object format is deprecated, according to the announcement. LWN flagged the same Python 3.4 removal and stabs deprecation.
GDB 17.2, the current release, is a maintenance update that delivers fixes and enhancements over GDB 17.1, resolving 14 reported issues, according to the 17.2 release announcement. The GDB news page lists version 17.2 as the latest version available for download.
Both releases were managed by Joel Brobecker, who signed the 17.1 announcement, as also noted by LWN.
What We Don’t Know
The announcements do not quantify adoption of the new control-flow-integrity debugging support, nor do they detail which distributions or vendor toolchains will ship GDB 17 by default. The release notes also do not specify a timeline for the next feature release in the series. The list of 14 issues fixed in 17.2 is enumerated in the announcement, but the project does not characterize their relative severity.
Analysis
GDB rarely makes headlines, but the 17 series tracks a real shift in the platforms it has to debug. As processor vendors push control-flow-integrity features from optional hardening toward default-on protections, a debugger that cannot reason about shadow stacks or Guarded Control Stacks becomes a liability for anyone debugging crashes in hardened binaries. Adding first-class support for both x86-64 and AArch64 mechanisms in the same series keeps GDB aligned with the security direction of the underlying hardware.
The continued investment in the Debugger Adapter Protocol points the other way — toward the editors and IDEs where many developers now expect to debug. A command-line tool from 1986 gaining DAP completion support is a quiet acknowledgment that GDB’s future includes being driven by front-ends as often as by its own prompt.