Closed
Bug 1626615
Opened 5 years ago
Closed 5 years ago
Fix debugger forced-return propagation for Ion frames
Categories
(Core :: JavaScript Engine: JIT, task, P2)
Core
JavaScript Engine: JIT
Tracking
()
RESOLVED
FIXED
mozilla76
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: jandem, Assigned: jandem)
References
Details
Attachments
(1 file)
This is triggered by jit-test/tests/debug/Frame-onStep-resumption-05.js
with WarpBuilder enabled.
In HandleExceptionIon we check whether the realm is a debuggee, but this doesn't handle the case where the realm is no longer a debuggee but we're still propagating a forced return.
Updated•5 years ago
|
Priority: -- → P2
Assignee | ||
Comment 1•5 years ago
|
||
With WarpBuilder enabled we failed the Frame-onStep-resumption-05.js jit-test. This
failed because when we are propagating a forced-return and turn off the debugger,
we ignored this forced-return for Ion frames. This patch fixes that test failure.
It also tidies up the code with a ShouldBailoutForDebugger helper function.
Pushed by jdemooij@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4d282675fe94
Fix forced-return propagation for Ion frames after debugger has been disabled. r=loganfsmyth
Comment 3•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox76:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
You need to log in
before you can comment on or make changes to this bug.
Description
•