Closed Bug 630770 Opened 9 years ago Closed 9 years ago
"Assertion failure: !p
options('strict') Function("function y(x,x)d") asserts js debug shell on TM changeset 3b3710520c0e at Assertion failure: !p.found(), without -m nor -j.
This also occurs on Linux and is a frequent occurrence for fuzzers. autoBisect shows this is probably related to the following changeset: The first bad revision is: changeset: 61758:4cb688939afc user: Jeff Walden date: Wed Jan 26 16:46:38 2011 -0800 summary: Bug 629187 - Strict mode keywords are accepted as argument names and function name for strict mode functions. r=jimb
OS: Windows 7 → All
Hardware: x86 → All
The test is a lie, kind of. There's no way to check that the warning happened, and that it happened only once, without hacking at the shell error reporter, and I'm not interested in spending time to do that now. This works as a don't-assert test, I'm moving on.
Attachment #509040 - Flags: review?(jimb)
Comment on attachment 509040 [details] [diff] [review] Patch and half-test The test should have a comment explaining that it's trying to provoke an assertion. r=me with that.
Attachment #509040 - Flags: review?(jimb) → review+
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla2.0b12
blocking2.0: ? → betaN+
Whiteboard: [fixed-in-tracemonkey] → [fixed-in-tracemonkey][softblocker]
cdleary-bot mozilla-central merge info: http://hg.mozilla.org/mozilla-central/rev/e518c56eaffd
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Automatically extracted testcase for this bug was committed: https://hg.mozilla.org/mozilla-central/rev/efaf8960a929
You need to log in before you can comment on or make changes to this bug.