[jsdbg2] Debugger.Frames are dumb about suspended generators
Categories
(Core :: JavaScript: Debugger API, enhancement, P2)
Tracking
()
People
(Reporter: jimb, Unassigned)
References
(Blocks 2 open bugs)
Details
When a generator frame is suspended, many accessors on Debugger.Frame fail to work, even though the information is readily available from the generator object.
The following accessors can be implemented by consulting the generator object:
- arguments
- callee
- environment
- script
The following may take some care to, but should still be recoverable:
- offset
- this
The following are trivial to implement, simply by knowing that the frame is a
suspended generator call:
- constructing
- generator
- type
- implementation
Comment 1•7 years ago
•
|
||
This is a duplicate of bug 1477063. I think I implemented all the items mentioned in comment 0 here, although there was some reason I never landed it, some regression I have forgotten. There are some tests in part 7 there, and a list of more tests I thought would be appropriate.
Updated•7 years ago
|
Updated•5 years ago
|
Updated•3 years ago
|
Comment 2•1 month ago
|
||
Moving bugs to Debugger API component. Use castle-terms-potato to filter out.
Description
•