Make sure ExternalCallbackScope is always created when VM state changes to EXTERNAL
authoryurys@chromium.org <yurys@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 20 Jun 2013 14:47:35 +0000 (14:47 +0000)
committeryurys@chromium.org <yurys@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 20 Jun 2013 14:47:35 +0000 (14:47 +0000)
commitc7b3ef0e05682613cfbb8eb1b7e4236871ccccf5
treea6e9f1a89ceeb0f9c0f0276516c6a45fbbfaba0a
parent6ae544eca7e3ea4a9535dab31da8d308e913c72f
Make sure ExternalCallbackScope is always created when VM state changes to EXTERNAL

ExternalCallbackScope is used to let CPU profiler know which API callback is being executed. Whenever such callback is called we should create VMState<ETERNAL> and ExternalCallbackScope. This patch fixes several places where VMState<ETERNAL> went without ExternalCallbackScope.

BUG=244580
R=dcarney@chromium.org, svenpanne@chromium.org

Review URL: https://codereview.chromium.org/17059005

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@15249 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/arguments.cc
src/builtins.cc
src/handles.cc
src/objects.cc
src/stub-cache.cc
test/cctest/test-api.cc