Reviewers: Mads Ager, Message: Begin to handle EXTERNAL (outside V8) states separately from OTHER (in V8 but not in JS, GC, or COMPILER).
With this change, it is possible to get into the EXTERNAL state via a callback out of the VM, and not be able to get back in through the API. That is expected. It can only happen when V8 is built with ENABLE_HEAP_PROTECTION and run with --protect-heap. Description: Mark some of the places we leave V8 via callbacks as transitions to state EXTERNAL rather than OTHER. Please review this at http://codereview.chromium.org/55007 SVN Base: http://v8.googlecode.com/svn/branches/bleeding_edge/ Affected files: M src/builtins.cc M src/handles.cc M src/log.cc M src/objects.cc M src/stub-cache.cc M src/top.cc M test/cctest/testcfg.py tools/tickprocessor.py --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
