Hi, I figured out a way to do this. Going by the way how multiple tags are debugged using the remote debugging in chrome, I displayed different links for each isolate in the index page (that is loaded on 9222). Based on which link is clicked, I checked the querystring part, which I made different for different isolates, the messages are redirected to the corresponding isolate wrapper.
I am not sure if there are any drawbacks for this approach. If I open each inspectable page in a new tab, I am also able to debug parallelly. Please provide your thoughts about this. regards, Anoop R. S. On Thursday, 25 May 2017 11:06:20 UTC+5:30, Anoop R. S. wrote: > > Thank you for replying, Ian. > I guess you are using something which uses node.js. But my case is > different. We have embedded v8 into our application without any node.js > involved. > I guess the correct way is to use a separate port for each v8::isolate and > redirect the json messages to each isolate correctly. > > regards, > Anoop R. S. > > On Thursday, 25 May 2017 10:45:52 UTC+5:30, Ian Bull wrote: >> >> 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.
