Open
Bug 996265
Opened 10 years ago
Updated 3 months ago
[jsdbg2] ScriptFrameIters stored in Debugger.Frame instances should never be done
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: jimb, Unassigned)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
1.60 KB,
patch
|
sfink
:
review+
|
Details | Diff | Splinter Review |
The ScriptFrameIter represented by a Debugger.Frame instance should never be '.done()'; we should assert this. (Marking this as 'blocking' bug 961325, but it's really just 'related'; that could land before this.)
Reporter | ||
Comment 1•10 years ago
|
||
Try push: https://tbpl.mozilla.org/?tree=Try&rev=d4dfe0a8a2d9
Attachment #8406461 -
Flags: review?(sphink)
Comment 2•10 years ago
|
||
Comment on attachment 8406461 [details] [diff] [review] Assert that iters from Debugger.Frame instances actually refer to something. Review of attachment 8406461 [details] [diff] [review]: ----------------------------------------------------------------- Seems reasonable, though all this frame munging code frightens me.
Attachment #8406461 -
Flags: review?(sphink) → review+
Comment 3•10 years ago
|
||
(In reply to Steve Fink [:sfink] from comment #2) > Comment on attachment 8406461 [details] [diff] [review] > Assert that iters from Debugger.Frame instances actually refer to something. > > Review of attachment 8406461 [details] [diff] [review]: > ----------------------------------------------------------------- > > Seems reasonable, though all this frame munging code frightens me. In the words of mccr8, welcome to adventure.
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
•