Closed
Bug 675581
Opened 14 years ago
Closed 14 years ago
"Assertion failure: js_CheckForStringIndex(id) == id" with e4x
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
VERIFIED
FIXED
mozilla8
People
(Reporter: gkw, Assigned: jorendorff)
Details
(Keywords: assertion, regression, testcase)
Attachments
(2 files)
4.45 KB,
text/plain
|
Details | |
2.07 KB,
patch
|
Waldo
:
review+
|
Details | Diff | Splinter Review |
x=<x/>
x.(-0 in x)
asserts js debug shell on MI changeset b4165ae3685f without any CLI arguments at Assertion failure: js_CheckForStringIndex(id) == id,
autoBisect shows this is probably related to the following changeset:
The first bad revision is:
changeset: 73438:cad13a541e30
user: Jason Orendorff
date: Wed Jul 27 17:44:29 2011 -0500
summary: Bug 651940 - When hashing a jsid, assert that js_CheckForStringIndex(id) == id. r=Waldo.
![]() |
||
Updated•14 years ago
|
Whiteboard: js-triage-needed
![]() |
Assignee | |
Comment 1•14 years ago
|
||
This invariant is old. Only the assertion is new in that revision.
This is probably a very old bug. Removing the bugzilla dependency.
Looking into it.
No longer blocks: 651940
![]() |
Assignee | |
Comment 2•14 years ago
|
||
Here E4X is using a function whose only other caller is JS_Alias*. Whee.
Assignee: general → jorendorff
Attachment #550568 -
Flags: review?(jwalden+bmo)
Updated•14 years ago
|
Attachment #550568 -
Flags: review?(jwalden+bmo) → review+
![]() |
Assignee | |
Updated•14 years ago
|
Summary: "Assertion failure: js_CheckForStringIndex(id) == id," with e4x → "Assertion failure: js_CheckForStringIndex(id) == id" with e4x
![]() |
Assignee | |
Comment 3•14 years ago
|
||
Whiteboard: js-triage-needed → [inbound]
Comment 4•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [inbound]
Target Milestone: --- → mozilla8
Comment 5•12 years ago
|
||
A testcase for this bug was automatically identified at js/src/tests/js1_8_5/regress/regress-675581.js.
Flags: in-testsuite+
![]() |
Reporter | |
Comment 6•12 years ago
|
||
Testcases have been landed by virtue of being marked in-testsuite+ -> VERIFIED as well.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•