On Thu, 2026-03-26 at 16:32 -0700, Florian Fainelli wrote: > 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 <[email protected]> > Signed-off-by: Florian Fainelli <[email protected]> > --- > 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 <command-name>" for commands and > "help > function <function-name>" 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
Reviewed-by: Radu Rendec <[email protected]>
