Open
Bug 662377
Opened 14 years ago
Updated 2 years ago
Check the entire stack when looking at debug frames
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
NEW
People
(Reporter: dcamp, Unassigned)
References
(Blocks 1 open bug)
Details
There are at least two places (Debug::getYoungestFrame() and the THIS_FRAME macro) where we assume debuggee frames are in the context's current stack.
This isn't always the case (when implementing the debugging protocol in firefox, we can end up with new contexts in event handlers).
|
Reporter | |
Comment 1•14 years ago
|
||
jorendorff fixed getYoungestFrame in http://hg.mozilla.org/users/jblandy_mozilla.com/jsdbg2/rev/720b3fe3c84e but this was backed out for depending on some other changesets. It doesn't look like this would be hard to backport to the current state of things.
|
Assignee | |
Updated•13 years ago
|
Component: JavaScript Debugging/Profiling APIs → JavaScript Engine
|
||
Comment 2•13 years ago
|
||
What's the status of this bug? Is it still a problem?
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•