Revision: 4378
Author: peter.rybin
Date: Fri Apr 9 06:29:38 2010
Log: Edited wiki page through web user interface.
http://code.google.com/p/v8/source/detail?r=4378
Modified:
/wiki/AddDebuggerSupport.wiki
=======================================
--- /wiki/AddDebuggerSupport.wiki Fri Apr 9 06:25:45 2010
+++ /wiki/AddDebuggerSupport.wiki Fri Apr 9 06:29:38 2010
@@ -29,9 +29,9 @@
Based on your current synchronization model, you may choose one of the two
approaches.
-*A. Your application already deals with multi-threaded synchronization.*
Everything is straightforward: call _!SetDebugMessageDispatchHandler_ with
the second argument “_provider_locker_” set to false. From your callback,
do not call _!ProcessDebugMessages_ method directly; you must schedule this
call for another thread instead.
-
-*B. Your application does not have a proper synchronization tool smith*.
It would take a lot to implement scheduling from one thread to another
thread. Then simply take advantage of V8 lockers. Just wrap all of your
calls to V8 with _v8::Locker_ (and possibly unwrap nested calls with
_v8::Unlocker_); it should not be too expensive. Install a callback in the
_!SetDebugMessageDispatchHandler_ method with the second argument
“_provider_locker_” set to true. From your callback, you may directly call
the _!ProcessDebugMessages_ method, though you have to set up a
_v8::Context_ first.
+*A. Your application already deals with multi-threaded synchronization.*
Everything is straightforward: call _!SetDebugMessageDispatchHandler_ with
the second argument _“provider_locker”_ set to false. From your callback,
do not call _!ProcessDebugMessages_ method directly; you must schedule this
call for another thread instead.
+
+*B. Your application does not have a proper synchronization tool smith*.
It would take a lot to implement scheduling from one thread to another
thread. Then simply take advantage of V8 lockers. Just wrap all of your
calls to V8 with _v8::Locker_ (and possibly unwrap nested calls with
_v8::Unlocker_); it should not be too expensive. Install a callback in the
_!SetDebugMessageDispatchHandler_ method with the second argument
_“provider_locker”_ set to true. From your callback, you may directly call
the _!ProcessDebugMessages_ method, though you have to set up a
_v8::Context_ first.
==Sample application lineprocessor.cc==
@@ -42,7 +42,7 @@
{{{
scons sample=lineprocessor
}}}
-(Add “_mode=debug_” if you want lineprocessor to work under a C++
debugger).
+(Add _“mode=debug”_ if you want lineprocessor to work under a C++
debugger).
Put a small program in a .js file, e.g. _capitalizer.js_:
{{{
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
To unsubscribe, reply using "remove me" as the subject.
