On Tue, Aug 16, 2016 at 1:10 PM, Abhishek Singh <[email protected]> wrote: > Hi, > > I’m using V8 Debugger, but facing an issue. > > https://gist.github.com/abhi-bit/20b8569bc5d655659b51d425564eb49d - this is > link to standalone code simulating the same problem. In short, what this > code does is: > > * Main thread i.e. the calling JS code with required params periodically. > Given it’s Local<Function> Call, I’m using V8::Locker(without it handlescope > errors out asking me to use locking api) > * Debug thread, that basically sets breakpoint -> list breakpoints and > finally clears the breakpoints in that order(with some sleep pause in > between the call), this too is using Locker and hence leading to the problem > I’m facing. > > In the given test case, main thread keeps running for first 10 secs and > doesn’t let Debug thread to proceed(because main thread has a lock for the > isolate) - so essentially I can’t do debug operations from another thread. > How can I avoid using locker in either main and debug threads or both and > debug user supplied JS code at runtime? Looking at v8 debug unit tests, I > don’t see it using locker anywhere in there. > > Thanks, > Abhishek
Your threads should not sleep while holding the Locker. Let it go out of scope before calling this_thread::sleep_for(). You could create a v8::Unlocker instance but you need to exit the Context scope first so letting the Locker go out of scope is probably just as easy. -- -- 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.
