From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6B5F237700F; Mon, 30 Mar 2026 16:15:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.79.88.28 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774887355; cv=none; b=oV4EdSzNNa7DBR5uMfw0aa7lMjc3aLdxl2NAlxIlyvOt/fc+rQgZoaPR91xAMNNZ2xb3VynggNr7YS9wdoH8C6WQEJsnS+CL5jheyXtIOHHJ6jWu2X4dXJuBuPw6gi6LsgFH9PgnEoevuRXIlVWfxGpDqk4FHvdLO3hAd9ey0eQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774887355; c=relaxed/simple; bh=BtXI0mQao2y5Gas//5IlwF4zRYP1UpwGL3ZM15UiWuk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=SB3GVfb2w91AF1L6mlOT5I7e5QALxNhcu04GV+CVsD5hqVZgxBKqeOc8eaAxUjDLPLMaBFF5umF+sbqvYq8BXGLa6K45J7ksfVUa16aBgW32UM6pDpJWeUBE94L1HEv7Xepy2Sxu9wbXNCrSymwUnrP0Jzm+Z3ChWWSQT9clHrc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net; spf=pass smtp.mailfrom=lwn.net; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b=ltp9k8io; arc=none smtp.client-ip=45.79.88.28 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lwn.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b="ltp9k8io" DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net 99343411C2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1774887353; bh=14wIG45328K8CYuQ29VhCJsnVScrNmHBwd15EFB7ZoQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=ltp9k8ioHtudZwy8CkXoWsoIv8I0SFvGJx/J01r4ZBiWpQQxFzKVI3gCFnBqhNstj aF97/pWSylZ+hNQkeC+Sx9JHB6HnlFOhHMAXDa5skIO5caMXR8sv2D3l3u0zjxuJGL rsBdSj+1N4Nnd/oaVrnG+Ip9kRrN8q2l4MrMmmzmHLxukHTAr0a1+Gq1xaxvovQ1xf DULF/gbBJHkpB2+YYF4J2PcAbi50bvAnrYUaJrc9/Oyv7fKIN4DwOhiYFEINU9QO2v Ee1Pnf/JAmjezi7wgyhkrMjctbiEVybc3xkghx1PXxRch2kgmoE9hqBMBNkC9p8zuA rU+SKmCquCWPg== Received: from localhost (mdns.lwn.net [45.79.72.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 99343411C2; Mon, 30 Mar 2026 16:15:53 +0000 (UTC) From: Jonathan Corbet To: Florian Fainelli , linux-kernel@vger.kernel.org, akpm@linux-foundation.org Cc: tglx@kernel.org, radu@rendec.net, Florian Fainelli , Shuah Khan , Illia Ostapyshyn , "open list:DOCUMENTATION PROCESS" , "open list:DOCUMENTATION" Subject: Re: [PATCH] Documentation: Provide hints on how to debug Python GDB scripts In-Reply-To: <20260326233226.2248817-1-florian.fainelli@broadcom.com> References: <20260326233226.2248817-1-florian.fainelli@broadcom.com> Date: Mon, 30 Mar 2026 10:15:52 -0600 Message-ID: <87mrzpnvif.fsf@trenco.lwn.net> Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Florian Fainelli writes: > 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 > --- > 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 Applied, thanks. jon