From 7f7f468548cee80d221cbc77e639fe99e113ff99 Mon Sep 17 00:00:00 2001 From: Florian Fainelli Date: Thu, 26 Mar 2026 16:32:24 -0700 Subject: [PATCH] Documentation: Provide hints on how to debug Python GDB scripts By default GDB does not print a full stack of its integrated Python interpreter, thus making the debugging of GDB scripts more painful than it has to be. Suggested-by: Radu Rendec Signed-off-by: Florian Fainelli Reviewed-by: Radu Rendec Signed-off-by: Jonathan Corbet Message-ID: <20260326233226.2248817-1-florian.fainelli@broadcom.com> --- Documentation/process/debugging/gdb-kernel-debugging.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/Documentation/process/debugging/gdb-kernel-debugging.rst b/Documentation/process/debugging/gdb-kernel-debugging.rst index 9475c759c722..53e225760a4d 100644 --- a/Documentation/process/debugging/gdb-kernel-debugging.rst +++ b/Documentation/process/debugging/gdb-kernel-debugging.rst @@ -173,3 +173,12 @@ this is just a snapshot of the initial version:: Detailed help can be obtained via "help " for commands and "help function " for convenience functions. + +Debugging GDB scripts +--------------------- + +GDB does not enable a full Python backtrace which can make debugging GDB +scripts more difficult than necessary. The following will allow for printing a +full backtrace of the python environment:: + + (gdb) set python print-stack full