Closed Bug 380018 Opened 18 years ago Closed 16 years ago

"Assertion failure: pcdepth >= 0" with return in finally

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jruderman, Unassigned)

Details

(Keywords: assertion, regression, testcase)

js> (function() { try { try { } finally { return; } } finally { this.z.z; } })() Assertion failure: pcdepth >= 0, at jsopcode.c:4869 Thread 0 Crashed: 0 js 0x000ca43a JS_Assert + 70 (jsutil.c:60) 1 js 0x000972df js_DecompileValueGenerator + 2447 (jsopcode.c:4871) 2 js 0x00026c95 js_ReportValueErrorFlags + 151 (jscntxt.c:1232) 3 js 0x00085cdd js_ValueToNonNullObject + 117 (jsobj.c:4581) 4 js 0x00068b75 js_Interpret + 55592 (jsinterp.c:3782) 5 js 0x0005a3dd js_Execute + 715 (jsinterp.c:1591) 6 js 0x0001b1c2 JS_ExecuteScript + 54 (jsapi.c:4702) 7 js 0x00002812 Process + 912 (js.c:268) 8 js 0x0000321b ProcessArgs + 2045 (js.c:519) 9 js 0x000080e0 main + 612 (js.c:3237) 10 js 0x00002326 _start + 216 11 js 0x0000224d start + 41
This testcase seems to work as expected in TM tip, but still occurs in 1.9.0.x branch.
Summary: "Assertion failure: pcdepth >= 0" with return in finally → [1.9.0.x branch] "Assertion failure: pcdepth >= 0" with return in finally
Version: Trunk → 1.9.0 Branch
(In reply to comment #1) > This testcase seems to work as expected in TM tip, but still occurs in 1.9.0.x > branch. Resolving as WFM would be a better resolution.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Summary: [1.9.0.x branch] "Assertion failure: pcdepth >= 0" with return in finally → "Assertion failure: pcdepth >= 0" with return in finally
Version: 1.9.0 Branch → Trunk
Flags: in-testsuite?
You need to log in before you can comment on or make changes to this bug.