Closed
Bug 510783
Opened 15 years ago
Closed 15 years ago
"Assertion failure: !(pn->pn_dflags & flag), at ../jsparse.h"
Categories
(Core :: JavaScript Engine, defect, P2)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla1.9.2
| Tracking | Status | |
|---|---|---|
| status1.9.2 | --- | beta1-fixed |
| status1.9.1 | --- | wanted |
People
(Reporter: gkw, Assigned: brendan)
References
Details
(Keywords: assertion, regression, testcase, Whiteboard: fixed-in-tracemonkey)
Attachments
(1 file)
|
(deleted),
patch
|
mrbkap
:
review+
|
Details | Diff | Splinter Review |
function () {
for (let[x] = ({
set s() {
yield x = e
},
l: x
}) in []);
}
asserts js debug shell on TM branch without -j at Assertion failure: !(pn->pn_dflags & flag), at ../jsparse.h:664
autoBisect shows this is probably related to bug 496134 :
The first bad revision is:
changeset: 28945:2e6025415fb3
user: Brendan Eich
date: Fri Jun 05 16:14:00 2009 -0700
summary: Fix destructuring binding to follow the cheezy dominance relation rules of the upvar analysis (496134, r=mrbkap).
Flags: blocking1.9.2?
|
Assignee | |
Updated•15 years ago
|
Assignee: general → brendan
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla1.9.2
|
Reporter | |
Updated•15 years ago
|
status1.9.1:
--- → ?
|
||
Updated•15 years ago
|
Flags: blocking1.9.2? → blocking1.9.2+
|
|
Assignee | |
Comment 1•15 years ago
|
||
Attachment #401361 -
Flags: review?(mrbkap)
|
||
Updated•15 years ago
|
Attachment #401361 -
Flags: review?(mrbkap) → review+
|
|
Assignee | |
Comment 2•15 years ago
|
||
Whiteboard: fixed-in-tracemonkey
|
|
Assignee | |
Comment 3•15 years ago
|
||
Followup, with r=mrbkap over irc:
http://hg.mozilla.org/tracemonkey/rev/ebdcce1c4cb7
/be
|
|
||
Comment 4•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
|
|
||
Comment 5•15 years ago
|
||
|
|
||
Comment 6•15 years ago
|
||
status1.9.2:
--- → beta1-fixed
|
|
Reporter | |
Updated•15 years ago
|
blocking1.9.1: --- → ?
|
||
Updated•15 years ago
|
blocking1.9.1: ? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•