This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/10682] New: gdb.backtrace doesn't handle reloading well
- From: "jason dot orendorff at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 21 Sep 2009 22:15:08 -0000
- Subject: [Bug python/10682] New: gdb.backtrace doesn't handle reloading well
- Reply-to: sourceware-bugzilla at sourceware dot org
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.