Reviewers: Mads Ager, Message: Most of this change involves moving code from the DebuggerMessageThread to Debugger where it can be called without the mesage thread beeing created. Most of the moved code was called from the Debugger anyway so having it in Debugger makes most sense anyway.
Description: Debugger message handler can be called from V8 thread. The message handler function set through the debugger API is normally called in a different thread than the V8 thread where execution is stopped due to debugger event. This change adds an option to the API for specifying that the message handler should be called directly from the V8 thread. For an application like Chrome where thread dispatching is already in place this makes more sense. Add an option to the message handler debugger API to process messages in the thread where V8 is running instead of posting it to a queue for processing on a additional thread. Please review this at http://codereview.chromium.org/42643 SVN Base: http://v8.googlecode.com/svn/branches/bleeding_edge/ Affected files: M include/v8-debug.h M src/api.cc M src/debug.h M src/debug.cc --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
