Fix a few issues breaking cctest/test-lockers/Regress1433:
authorvitalyr@chromium.org <vitalyr@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 5 Jul 2011 15:49:39 +0000 (15:49 +0000)
committervitalyr@chromium.org <vitalyr@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 5 Jul 2011 15:49:39 +0000 (15:49 +0000)
commitbbaed5b82e3531506481fd89e531da9e3c74a9c7
treeab8574264712d339385536701c5362b3a26e1022
parent798009cf1aba6e46ab852d63bc6c0eebcd5ef2c5
Fix a few issues breaking cctest/test-lockers/Regress1433:

o The thread local state in an isolate has to be initialized before
  it's used.
o v8::Locker was incorrectly tracking whether it's the topmost one.
o Waking the profiler thread on shutdown should not leave the
  semaphore counter in an inconsitent state.

R=fschneider@chromium.org
BUG=v8:1522
TEST=cctest/test-lockers/Regress1433

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8537 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
13 files changed:
src/execution.cc
src/isolate.cc
src/isolate.h
src/platform-cygwin.cc
src/platform-freebsd.cc
src/platform-linux.cc
src/platform-macos.cc
src/platform-openbsd.cc
src/platform-solaris.cc
src/platform-win32.cc
src/runtime-profiler.cc
src/runtime-profiler.h
src/v8threads.cc