When I originally asked this question it was about the debug agent. That agent no longer exists.
I now use the JS debugger that's available in V8. You can set a flag (something like "expose-debug-as=__j2v8_debug_handler"). This is what I use in J2V8 and there is a debug handler registered in the global scope called __j2v8_debug_handler. I can then add breakpoints, and interact with the debugger using JavaScript against this object. Cheers, Ian On Wednesday, 24 May 2017 21:06:07 UTC-7, Zac Hansen wrote: > > How would that work if you had multiple isolates running simultaneously in > multiple threads? > > I like the model of keeping isolates completely separate as much as > possible. > > On Thursday, May 18, 2017 at 9:20:02 PM UTC-7, Anoop R. S. wrote: >> >> I would like to enable debug support for each isolate (with a different >>> port). >>> >> >> Does it have to be a separate port for each isolate ? (if you are talking >> about the websocket port where the debugger is exposed, it would be 9222 >> usually) >> If that is the case, I guess you would be generating new port numbers for >> each new v8::isolate that is to be debugged. >> >> Am I getting it correctly? >> >> Is there any way around that? Could we achieve the debugging of multiple >> v8::isolate by exposing the websocket service in a single port? >> >> >> regards, >> Anoop R. S. >> > -- -- 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.
