This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/21436] New: frame filter should allow duplicated underlying frames
- From: "tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 26 Apr 2017 22:07:38 +0000
- Subject: [Bug python/21436] New: frame filter should allow duplicated underlying frames
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=21436
Bug ID: 21436
Summary: frame filter should allow duplicated underlying frames
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: python
Assignee: unassigned at sourceware dot org
Reporter: tromey at sourceware dot org
Target Milestone: ---
Currently a frame filter must associate each frame it returns with
some underlying inferior frame. If multiple decorated frames refer
to the same underlying frame, the resulting output from gdb is a bit
funny -- it prints the frame number (like "#5") just once, but otherwise
prints the entire frame multiple times (at each spot it is referenced).
(It's possible this only occurs when the frame is also elided -- I
can't recall right now.)
This problem came up while writing a frame filter that understands
SpiderMonkey interpreter frames. See:
https://bugzilla.mozilla.org/show_bug.cgi?id=1254297
In SpiderMonkey, a given invocation of the interpreter loop may actually
evaluate several interpreted calls, so each such frame would refer
to the same underlying C++ frame.
--
You are receiving this mail because:
You are on the CC list for the bug.