You can take a look at test/inspector/inspector-test.cc to see how to attach an inspector client to a V8 context. By patching this through to a socket, you could use Chrome to debug.
On Tuesday, October 18, 2016 at 10:41:01 AM UTC+2, Zac Hansen wrote: > > Looking at the bug, less than 2 hours ago I see: > > [inspector] Turn on inspector by default > > > Not sure if that means what I think it means, but maybe it's ready to go? > > On Tuesday, October 18, 2016 at 1:39:48 AM UTC-7, Zac Hansen wrote: >> >> bad news: there is currently no way to do this. >> >> good news: there is active work on it. >> >> From a thread I was on a week ago or so: >> > The V8 inspector migration is almost complete--the majority of work >> has been done. You can follow development in the source >> <https://github.com/v8/v8/tree/master/src/inspector> repo and via this >> bug <https://bugs.chromium.org/p/chromium/issues/detail?id=635948>. Upon >> completion we will document usage on the V8 GitHub wiki. >> >> >> >> On Tuesday, October 18, 2016 at 1:27:27 AM UTC-7, Richard Pike wrote: >>> >>> I know this question has been somewhat answered before but I am scouting >>> round for some more definitive pointer's on how to get this done. I >>> currently Run many v8 isolate on many threads. Each thread runs its own >>> set of scripts within a single isolate. >>> >>> I want to attach a debugger to one (or more) of the isolates. Is there >>> a way (like the JVM) to turn on debugging (activate a TCP port) and attach >>> an external debugger? >>> >>> Richard >>> >> -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
