From: Diego Russo <diego.russo@arm.com>
Date: Thu, 7 May 2026 13:05:29 +0000 (+0100)
Subject: gh-126910: Update 3.15 what's new to include GDB/backtrace integration (#149494)
X-Git-Tag: v3.15.0b1~1
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=299cf3c4974262c63694195e605a66856c5a329a;p=thirdparty%2FPython%2Fcpython.git

gh-126910: Update 3.15 what's new to include GDB/backtrace integration (#149494)

Update 3.15 what's new to include GDB/backtrace intergration
---

diff --git a/Doc/whatsnew/3.15.rst b/Doc/whatsnew/3.15.rst
index 50ce22c4e91f..9e2f789334ff 100644
--- a/Doc/whatsnew/3.15.rst
+++ b/Doc/whatsnew/3.15.rst
@@ -1903,6 +1903,7 @@ The major upgrades to the JIT are:
 * New tracing frontend
 * Basic register allocation in the JIT
 * More JIT optimizations
+* GDB and GNU ``backtrace()`` unwinding support
 * Better machine code generation
 
 .. rubric:: LLVM 21 build-time dependency
@@ -1954,6 +1955,17 @@ reference count updates and perform in-place operations on ints and floats.
 The JIT optimizer now supports significantly more operations than in 3.14.
 (Contributed by Kumar Aditya, Ken Jin, Jiahao Li, and Sacul in :gh:`131798`.)
 
+.. rubric:: GDB and GNU ``backtrace()`` unwinding support
+
+The JIT compiler now publishes unwind information for generated machine code to the
+GDB interface on supported Linux ELF platforms. When libgcc frame
+registration is available, the same unwind information is also registered for
+GNU ``backtrace()`` stack walkers. This allows native debuggers, crash
+handlers, and diagnostic tools using these mechanisms to unwind through JIT
+frames instead of stopping at generated code.
+(Contributed by Diego Russo and Pablo Galindo Salgado in :gh:`146071` and
+:gh:`149104`.)
+
 .. rubric:: Better machine code generation
 
 The JIT compiler's machine code generator now produces better machine code