Closed
Bug 355049
Opened 18 years ago
Closed 18 years ago
decompilation of for..in destructuring into two holes causes "Assertion failure: pos != 0"
Categories
(Core :: JavaScript Engine, defect, P2)
Core
JavaScript Engine
Tracking
()
VERIFIED
FIXED
mozilla1.9alpha1
People
(Reporter: jruderman, Assigned: brendan)
References
Details
(Keywords: crash, testcase, verified1.8.1.1)
Attachments
(1 file)
1.40 KB,
patch
|
mrbkap
:
review+
dveditz
:
approval1.8.1.1+
|
Details | Diff | Splinter Review |
js> function () { [3 for ([, , ] in null)] } js> js> function () { [3 for each ([, , ] in null)] } js> In a debug build, I get "Assertion failure: pos != 0, at jsopcode.c:2512".
Reporter | ||
Comment 1•18 years ago
|
||
This is slightly different, in that the *initial value*, rather than the thing being destructured into, is two holes. Is this the same bug? js> for(var [[[]], x] = [,,] in {}) { } Assertion failure: j < n, at jsopcode.c:1133
Assignee | ||
Comment 2•18 years ago
|
||
Empty destructurers are allowed per the ES4 proposal, so JSOP_ARRAYPUSH's decompiler must cope. /be
Assignee | ||
Updated•18 years ago
|
Blocks: js1.7src
Flags: blocking1.8.1.1?
OS: Mac OS X 10.4 → All
Priority: -- → P2
Hardware: Macintosh → All
Target Milestone: --- → mozilla1.9alpha
Assignee | ||
Comment 3•18 years ago
|
||
(In reply to comment #1) > This is slightly different, in that the *initial value*, rather than the thing > being destructured into, is two holes. Is this the same bug? > > js> for(var [[[]], x] = [,,] in {}) { } > Assertion failure: j < n, at jsopcode.c:1133 Different bug, please file separately. /be
Reporter | ||
Comment 4•18 years ago
|
||
Comment 1 is now bug 355660.
Updated•18 years ago
|
Attachment #241425 -
Flags: review?(mrbkap) → review+
Assignee | ||
Updated•18 years ago
|
Attachment #241425 -
Flags: approval1.8.1.1?
Assignee | ||
Comment 5•18 years ago
|
||
Checking in jsopcode.c; /cvsroot/mozilla/js/src/jsopcode.c,v <-- jsopcode.c new revision: 3.191; previous revision: 3.190 done /be
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 6•18 years ago
|
||
Checking in regress-355049-01.js; /cvsroot/mozilla/js/tests/js1_7/regress/regress-355049-01.js,v <-- regress-355049-01.js initial revision: 1.1 done RCS file: /cvsroot/mozilla/js/tests/js1_7/regress/regress-355049-02.js,v done Checking in regress-355049-02.js; /cvsroot/mozilla/js/tests/js1_7/regress/regress-355049-02.js,v <-- regress-355049-02.js initial revision: 1.1 done
Flags: in-testsuite+
Updated•18 years ago
|
Flags: blocking1.8.1.1? → blocking1.8.1.1+
Comment 8•18 years ago
|
||
Comment on attachment 241425 [details] [diff] [review] fix approved for 1.8 branch, a=dveditz for drivers
Attachment #241425 -
Flags: approval1.8.1.1? → approval1.8.1.1+
Assignee | ||
Comment 9•18 years ago
|
||
Fixed on 1.8 branch: Checking in jsopcode.c; /cvsroot/mozilla/js/src/jsopcode.c,v <-- jsopcode.c new revision: 3.89.2.64; previous revision: 3.89.2.63 done /be
Keywords: fixed1.8.1.1
Comment 10•18 years ago
|
||
verified fixed 20061122 1.8.1.1 windows/linux/mac*, 1.9 windows/linux
Keywords: fixed1.8.1.1 → verified1.8.1.1
You need to log in
before you can comment on or make changes to this bug.
Description
•