Closed Bug 355002 Opened 18 years ago Closed 18 years ago

"Assertion failure: 0" at jsemit.c:4414

Categories

(Core :: JavaScript Engine, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

()

VERIFIED FIXED

People

(Reporter: jruderman, Assigned: brendan)

Details

(4 keywords)

Attachments

(1 file)

js> for each (this in []) { }
Assertion failure: 0, at jsemit.c:4414

This is a recent regression.  It also has bad effects in opt builds.
Attached patch fixSplinter Review
Sorry about that -- still tired. I need a vacation!

/be
Assignee: general → brendan
Status: NEW → ASSIGNED
Attachment #240784 - Flags: review?(mrbkap)
I took the liberty of fixing this very recent, very bad regression on the trunk and the 1.8 branch.

/be
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Keywords: fixed1.8.1
Resolution: --- → FIXED
Attachment #240784 - Flags: review?(mrbkap) → review+
Checking in regress-355002.js;
/cvsroot/mozilla/js/tests/js1_5/Regress/regress-355002.js,v  <--  regress-355002.js
initial revision: 1.1
done
Flags: in-testsuite+
I don't know what I or my builds were smoking when I tested this test or checked it in. It should have been in js16 or later since it uses for each and should have caught the syntax error. I would appreciate it if someone would review and make sure it is correct.

Removing js1_5/Regress/regress-355002.js;
/cvsroot/mozilla/js/tests/js1_5/Regress/regress-355002.js,v  <--  regress-355002.js
new revision: delete; previous revision: 1.1
done
RCS file: /cvsroot/mozilla/js/tests/js1_6/Regress/regress-355002.js,v
done
Checking in js1_6/Regress/regress-355002.js;
/cvsroot/mozilla/js/tests/js1_6/Regress/regress-355002.js,v  <--  regress-355002.js
initial revision: 1.1
done
verified fixed 20061003 1.8 windows/mac*/linux 1.9 windows/linux
Status: RESOLVED → VERIFIED
Summary: "Assertion failure: 0, at jsemit.c:4414" → "Assertion failure: 0" at jsemit.c:4414
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: