Last Comment Bug 646600 - Incorrect behavior (and decompilation) when sharps are nearby
: Incorrect behavior (and decompilation) when sharps are nearby
Status: RESOLVED FIXED
: testcase
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: Trunk
: All All
: -- normal (vote)
: ---
Assigned To: general
:
: Jason Orendorff [:jorendorff]
Mentors:
Depends on:
Blocks: jsfunfuzz
  Show dependency treegraph
 
Reported: 2011-03-30 13:08 PDT by Jesse Ruderman
Modified: 2012-02-17 15:34 PST (History)
3 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Jesse Ruderman 2011-03-30 13:08:27 PDT
This was caught by jsfunfuzz round-trip checking.

js> (function() { var a = [1,,,]; return a; })()              
[1, , ,]
Correct

js> (function() { var a = [1,,,]; return a; })                
(function () {var a = [1, , , ];return a;})
Correct

js> (function() { var a = [1,,,]; return a; var b = #1#; })() 
[1]
Missing all the holes

js> (function() { var a = [1,,,]; return a; var b = #1#; })
(function () {var a = [1, , ];return a;var b = #1#;})
Missing one of the holes
Comment 1 Gary Kwong [:gkw] [:nth10sd] 2012-02-17 15:34:53 PST
Fixed by bug 566700, the removal of sharp variables.

Note You need to log in before you can comment on or make changes to this bug.