Currently I'm targeting 3.26 (I had trouble building 3.27 & 3.28 on both my Mac and for Android, although I can certainly revisit that).
I'll take a look at the new API. Thanks! Ian On Wednesday, 3 September 2014 13:00:50 UTC-7, Ben Noordhuis wrote: > > On Wed, Sep 3, 2014 at 6:58 PM, Ian Bull <[email protected] <javascript:>> > wrote: > > I've read a bit on enabling debug support with multiple isolates, but > I'm > > still struggling with the API [1]. > > > > [1] > https://groups.google.com/forum/#!msg/v8-users/7EuZOSVYTAs/ygryv0JdNvMJ > > > > In my case I have a single thread per isolate. I would like to enable > debug > > support for each isolate (with a different port). Isolates can come and > go. > > I've managed to Enable the Agent, and attach the > > DebugMessageDispatchHandler. However, when my callback is invoked I have > no > > idea what isolate it is for. This is important since I need to lookup > the > > isolate and synchronize with that thread in order to setup the proper > > context and ProcessDebugMessages. > > > > Without any parameters to the DispatchHandler, what is the proper way to > > figure out what isolate this callback is for? Even the name of the > embedding > > application or the debug port would be enough. I looked at some of the > other > > static methods (such as Isolate::GetCurrent -- this returns NULL), but > using > > these seems like a race condition waiting to happen. > > > > Thoughts? > > Ian > > What version of V8 are you targeting, Ian? The debug API has seen > significant changes recently. > -- -- 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.
