Hi, since it has not been used by Chromium and falling victim to bit rot, we are going to remove the debug agent that has - until now - been included in V8.
The debug agent is a thread that can be spun up to receive debug command messages via socket connection. This does not mean that V8's debugger protocol [0] is deprecated. On the contrary, debug messages in form of JSON strings can still be sent via v8::Debug::SendCommand and forced to be processed via v8::Debug::ProcessDebugMessages. As consequence, the following methods in the debug API are going to be removed: v8::Debug::SetDebugMessageDispatchHandler v8::Debug::EnableAgent v8::Debug::DisableAgent I would like to ask embedders who used the debug agent up until now to implement messaging via sockets by themselves. Sending debug messages to V8 from a thread other than the isolate's main thread is demonstrated in a newly introduced test case [1]. Best Regards, Yang [0] https://code.google.com/p/v8/wiki/DebuggerProtocol [1] https://codereview.chromium.org/279423004/diff/20001/test/cctest/test-debug.cc -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
