Re: Expose Frame Type and Stop Reason in python Unwinder API

Paul Koning via Gdb <[email protected]> Thu, 22 Aug 2024 09:09:46 -0400

Newsgroups	gmane.comp.gdb.devel
Message-ID	<[email protected]>


> On Aug 21, 2024, at 10:28 PM, Andrew Wock via Gdb <[email protected]> wrote:
> 
> Hello,
> 
> Recently I wrote a kernel trapframe unwinder using the python API, and
> I was able to successfully extract the registers from the trapframe.
> However, sometimes gdb would throw the "previous frame inner to this
> frame" error on me.  This is because unwinding a trapframe sometimes
> results in unwinding to a different stack.
> 
> The way this is fixed in the internal unwinder API is that there are
> special frame types such as SIGTRAMP_FRAME which don't get checked for
> that error.
> 
> Additionally, some trapframes unwind into userspace.  In those cases
> I'd like to be able to stop the backtrace by setting a stop reason.

For that case, stopping should be an option.  In the past I have found it very useful to be able to continue from kernel to user, in certain situations.

	paul