public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "plasmahh at gmx dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/28538] New: Consider adding possibility to call gdb unwinder for the heavy lifting
Date: Wed, 03 Nov 2021 15:16:42 +0000	[thread overview]
Message-ID: <bug-28538-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=28538

            Bug ID: 28538
           Summary: Consider adding possibility to call gdb unwinder for
                    the heavy lifting
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: plasmahh at gmx dot net
  Target Milestone: ---

When writing an python unwinder  the current approach is an "all or nothing"
kind. Often one does want to do a little more on top of what gdb would do, but
has to do it all on your own. It would be nice to be able to call the gdb
unwinder to "see what it says" and then to work from that on. Best possibly by
being able to call super().__call__(pending_frame) from within your own
__call__ (similar to frame decorators/filters)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-11-03 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 15:16 plasmahh at gmx dot net [this message]
2022-02-19 16:08 ` [Bug python/28538] " tromey at sourceware dot org
2022-02-19 20:32 ` plasmahh at gmx dot net

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=bug-28538-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).