Correctly materialize arguments object in Runtime_DebugEvaluate.
authoryangguo@chromium.org <yangguo@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 25 Mar 2013 10:01:53 +0000 (10:01 +0000)
committeryangguo@chromium.org <yangguo@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 25 Mar 2013 10:01:53 +0000 (10:01 +0000)
commitb347a0dcae9ccfbcbbbe070758024d9981af39f2
tree57e936a795803b0fdc831b74611cc997b459fc2c
parent3ac8bf41b42bef737878de9a627e1a464f308d3b
Correctly materialize arguments object in Runtime_DebugEvaluate.

The problem was that if the # arguments specified in the function
declaration and the # arguments passed to the function are not
the same, we use an arguments adapter frame to make it work. This
confuses the existing implementation to materialize the arguments
object.

R=peter.rybin@gmail.com
BUG=222893

Review URL: https://chromiumcodereview.appspot.com/12674027

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@14059 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/runtime.cc
test/mjsunit/regress/regress-crbug-222893.js [new file with mode: 0644]