Open
Bug 1445815
Opened 7 years ago
Updated 2 years ago
Debugger.Frame .eval("arguments") fails for generator frames with bogus error message
Categories
(Core :: JavaScript Engine, enhancement, P3)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: jorendorff, Unassigned)
References
(Blocks 1 open bug)
Details
let g = newGlobal();
g.eval('function indirection() { debugger; }');
g.eval('function* f() { print(uneval(indirection())); }');
let dbg = new Debugger(g);
dbg.onDebuggerStatement = frame => {
frame = frame.older; // drill down to f's frame
return frame.eval("arguments"); // this fails
};
g.f(1, 2, 3).next();
----
More generator-debugging weirdness. This throws an Error with the message "Debugger env is not live".
https://searchfox.org/mozilla-central/source/js/src/vm/EnvironmentObject.cpp#2038
DebugEnvironments::hasLiveEnvironment(env) is returning nullptr. I'm not sure why we can't have a live environment for a resumed generator frame.
Reporter | ||
Updated•7 years ago
|
Priority: -- → P3
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
•