Fix an assertion failure in stack trace construction.
authorkmillikin@chromium.org <kmillikin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 9 Feb 2011 11:45:50 +0000 (11:45 +0000)
committerkmillikin@chromium.org <kmillikin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 9 Feb 2011 11:45:50 +0000 (11:45 +0000)
commit991a1cae12fdba09f3afb456abcadc93fb3a5825
tree3a56598b6ee6983af68a5f4d48860d8b37e0920d
parentd724993138a7cb668b208b064ff08c3305b4eb76
Fix an assertion failure in stack trace construction.

When constructing stack traces we interpret the deoptimization data for
optimized frames to find the receiver value.  This value could sometimes be
eliminated from the deoptimization data if we though it was unused.

BUG=v8:1118

Review URL: http://codereview.chromium.org/6465023

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6694 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/hydrogen-instructions.cc
src/hydrogen-instructions.h
src/hydrogen.cc
test/mjsunit/regress/regress-1118.js [new file with mode: 0644]