Open
Bug 1549914
Opened 5 years ago
Updated 2 years ago
js::GetGeneratorObjectForFrame returns nullptr after generator object has been created
Categories
(Core :: JavaScript Engine, task, P2)
Core
JavaScript Engine
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | fix-optional |
People
(Reporter: jimb, Unassigned)
References
Details
GetGeneratorObjectForFrame returns nullptr between the GENERATOR and SETALIASEDVAR .generator bytecode instructions, creating a weird transient state for generators in which they do have an AbstractGeneratorObject, but it cannot be located from the frame.
Single-stepping in Debugger can make this state visible.
We could fix this by inspecting the next bytecode, and then just returning the generator off the top of the value stack.
|
||
Updated•5 years ago
|
status-firefox68:
--- → fix-optional
Priority: -- → P2
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•