News › linux
By The Linux Camp News, September 29, 2026
Existing type indexes need regeneration, while remote argument synchronization requires server support. Older saved execution records are incompatible with the new release.
Andrew Burgess announced GDB 18.1 on September 25, 2026. The GNU Debugger release is available as upstream source: GNU's download directory, retrieved September 29, lists both compressed source archives and detached signatures. That establishes source availability, not availability through a Linux distribution's package repositories. 4 3
For engineers using .gdb_index sections for symbol lookup, the release notes call for regenerating existing indexes. Previously, index-based lookup could miss a type; GDB now includes all type symbols when creating the index. The index version number has not changed, so checking that number alone cannot establish whether an existing index contains the corrected symbol coverage. 2
Remote sessions gain argument synchronization, but only when the server supports the new qExecAndArgs protocol packet. GDB copies the server's argument string into its own args setting. Engineers can inspect it with show args, and subsequent extended-remote runs reuse those arguments. The practical benefit is preserving the first run's arguments across reruns; changing the client alone does not guarantee this behavior. 2
Adding or cloning an inferior, GDB's debugging context for a program, also changes when the existing connection cannot be shared. Core-file and Windows-native connections are examples. Instead of attempting invalid sharing that the announcement says tended to crash GDB, the debugger warns and creates the new inferior without a connection. Automation must therefore account for that disconnected result. 4
Python extension authors gain structured access to loaded core files through gdb.Corefile and Inferior.corefile. Additional mapped-file and region types describe the files mapped when the core was created. These additions expose postmortem debugging information directly through the API. 4
Before changing debugging toolchains, check retained artifacts against the compatibility removals. GDB drops Common Trace Format support, .gdb_index versions below 7 and DWARF Package File version 1. Trace output uses GDB's tfile format exclusively. Separately, the saved execution-record format changes and previous formats are unsupported, so an archive of record-save sessions cannot be assumed readable by 18.1. 2 4