Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Koning via Gdb <gdb@sourceware.org>
To: Andrew Wock <ajwock@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Expose Frame Type and Stop Reason in python Unwinder API
Date: Thu, 22 Aug 2024 09:09:46 -0400	[thread overview]
Message-ID: <DC2E3888-6982-4559-B095-2FEF71532E3B@comcast.net> (raw)
In-Reply-To: <CAACtx1aThXELFEmbE3H=gjNqmBvGNwBiUka2u4ziyj_ji9psWA@mail.gmail.com>



> On Aug 21, 2024, at 10:28 PM, Andrew Wock via Gdb <gdb@sourceware.org> 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



  reply	other threads:[~2024-08-22 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22  2:28 Andrew Wock via Gdb
2024-08-22 13:09 ` Paul Koning via Gdb [this message]
2024-08-26 13:56 ` John Baldwin via Gdb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DC2E3888-6982-4559-B095-2FEF71532E3B@comcast.net \
    --to=gdb@sourceware.org \
    --cc=ajwock@gmail.com \
    --cc=paulkoning@comcast.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox