Try to simplify the semantics of the profiling code by making
authorkasperl@chromium.org <kasperl@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 18 Oct 2010 12:37:07 +0000 (12:37 +0000)
committerkasperl@chromium.org <kasperl@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 18 Oct 2010 12:37:07 +0000 (12:37 +0000)
commitcabe82959fb6a5fd177f14ab752c855ac38264bd
tree5665676e446b9b4815f7cc08471967bf477b7f26
parent767bded9939096e15ddb4dc9c4558afdd956a733
Try to simplify the semantics of the profiling code by making
sure to suspend the thread (if necessary) on mac/win32 before
reading the VM state.

Avoid dealing with signals delivered to non-VM threads on
linux no matter if we're profiling or not.
Review URL: http://codereview.chromium.org/3845006

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5641 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/log.cc
src/platform-linux.cc
src/platform-macos.cc
src/platform-win32.cc
src/platform.h
test/cctest/test-log.cc