Closed Bug 381107 Opened 17 years ago Closed 15 years ago

"Assertion failure: pcdepth >= 0" in js_DecompileValueGenerator after finally/break that isn't even used

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: jruderman, Unassigned)

Details

(Keywords: assertion, testcase) 

This assertion also shows up in bug 380018.

js> o = {set x(){}}; while(0) try { } finally { print(3); break; } o.x.x;
Assertion failure: pcdepth >= 0, at jsopcode.c:4885

Thread 0 Crashed:
0   js 	0x000ca352 JS_Assert + 70 (jsutil.c:60)
1   js 	0x000971f8 js_DecompileValueGenerator + 2447 (jsopcode.c:4887)
2   js 	0x000269f5 js_ReportValueErrorFlags + 151 (jscntxt.c:1232)
3   js 	0x00085b3c js_ValueToNonNullObject + 117 (jsobj.c:4576)
4   js 	0x00068905 js_Interpret + 55592 (jsinterp.c:3782)
5   js 	0x0005a16d js_Execute + 715 (jsinterp.c:1591)
6   js 	0x0001af07 JS_ExecuteScript + 54 (jsapi.c:4692)
7   js 	0x00002552 Process + 912 (js.c:268)
8   js 	0x00002f5b ProcessArgs + 2045 (js.c:519)
9   js 	0x00007e88 main + 612 (js.c:3260)
10  js 	0x00002066 _start + 216
11  js 	0x00001f8d start + 41
WFM in TM tip (but still asserts in latest 1.9.0.x branch)
Status: NEW → RESOLVED
Closed: 15 years ago
Flags: in-testsuite?
Keywords: assertion
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.