Hi Zac, Thank you for replying. Then how they do it for Chrome? I mean, we can open localhost:9222 and select the tabs that we want to inspect. I had a notion that each tab corresponds to separate v8::isolate.
regards, Anoop R. S. On Thursday, 25 May 2017 09:36:07 UTC+5:30, 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.
