Correctly set eval_from_shared value when new function is created by "new Function...
authoryurys@chromium.org <yurys@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 1 Feb 2010 12:56:56 +0000 (12:56 +0000)
committeryurys@chromium.org <yurys@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 1 Feb 2010 12:56:56 +0000 (12:56 +0000)
commit2a8034c8f6349d71812eed69704aa3250f744db7
treecdd26076b46185db060f9025e88a17b61f049b42
parentd450fe1ed3c159c8041d0625da281840d8bf8860
Correctly set eval_from_shared value when new function is created by "new Function(...)". At the moment it's set to the native script where the Function is defined(v8natives.js) which doesn't make much sense for the user when he tries to debug his code. Moreover, it causes an exception in JSONProtocolSerializer.prototype.serialize_.

Related Chromium bug: http://crbug.com/29062
Review URL: http://codereview.chromium.org/551227

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3755 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/compiler.cc
src/mirror-delay.js
test/mjsunit/debug-compile-event-newfunction.js [new file with mode: 0644]