public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jason dot orendorff at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/10682] New: gdb.backtrace doesn't handle reloading well Date: Mon, 21 Sep 2009 22:15:00 -0000 [thread overview] Message-ID: <20090921221506.10682.jason.orendorff@gmail.com> (raw) First, if push_frame_filter is called more than once, create_frame_filter dies. The lambda created in push_frame_filter calls itself recursively. Second, and more seriously, the gdb.backtrace.push_frame_filter API is not really suitable to be called by a Python extension at import time. It's effectful and non-idempotent. I hit both problems the first time I tried reload()ing a module that registers a frame filter. :-| It will be hard to fix without changing the API. The (untested) attachment attempts one gruesome hack, but I hope you can take a breaking API change instead. -- Summary: gdb.backtrace doesn't handle reloading well Product: gdb Version: archer Status: UNCONFIRMED Severity: normal Priority: P2 Component: python AssignedTo: unassigned at sourceware dot org ReportedBy: jason dot orendorff at gmail dot com CC: gdb-prs at sourceware dot org http://sourceware.org/bugzilla/show_bug.cgi?id=10682 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2009-09-21 22:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-09-21 22:15 jason dot orendorff at gmail dot com [this message] 2009-09-21 22:15 ` [Bug python/10682] " jason dot orendorff at gmail dot com 2009-09-23 22:13 ` tromey at redhat dot com 2009-09-23 22:15 ` tromey at redhat dot com 2009-09-23 22:15 ` tromey at redhat dot com 2010-06-30 9:05 ` pmuldoon at redhat dot com
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=20090921221506.10682.jason.orendorff@gmail.com \ --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: linkBe 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).