projects / platform / upstream / v8.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8f9f192) | patch
Fix unexpected stack traces in test-cpu-profiler/JsNativeJsSample
authoryurys@chromium.org <yurys@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 16 Oct 2013 08:15:06 +0000 (08:15 +0000)
committeryurys@chromium.org <yurys@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 16 Oct 2013 08:15:06 +0000 (08:15 +0000)
commit5b105b248ee10ab196b423a4e55a3c645bf8ea71
tree055bc7b9eed9d22827b75af10d727c75b501e8bftree | snapshot
parent8f9f192f6e9c7c2d36d69fd9d3d4b364e0046593commit | diff
Fix unexpected stack traces in test-cpu-profiler/JsNativeJsSample

This is a follow-up fix for r17140 which makes sure that cpu profiler is started before profiled js functions are compiled so that the profiler gets information about "no frame" ranges along with add code events.

BUG=v8:2933
R=jkummerow@chromium.org, loislo@chromium.org

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17229 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
test/cctest/cctest.status diff | blob | history
test/cctest/test-cpu-profiler.cc diff | blob | history
Domain: Web Framework / Web Engine;