Open
Bug 676903
Opened 13 years ago
Updated 2 years ago
[jsdbg2] Debugger.Frame.prototype.older should reveal non-debuggee frames
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
NEW
People
(Reporter: jorendorff, Unassigned)
References
(Blocks 1 open bug)
Details
Currently we just omit non-debuggee code from the stack, but that's crazy.
Edited for brevity:
<jimb> Yes, we should not simply omit frames for calls to non-debuggee code.
<jorendorff> like, suppose you call jquery's forEach method, passing it a
function.
<jorendorff> maybe forEach calls something else which calls something else
which then calls your function
<jorendorff> we could just show forEach, and no details
<jorendorff> basically a placeholder frame.
<jorendorff> don't show the other frames
<jimb> Yep.
<jimb> the idea was to treat non-debuggee code as an opaque primitive [hand-wave]
<jimb> You need to know what was called, but then everything younger than that
that stays within non-debuggee code is just "internal structure", until
you get to your debuggee callback.
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Updated•4 years ago
|
Blocks: js-debugger
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•