If I patch the DebugBreak function to use the current isolate (if any) instead of the default one, I correctly break on the first JS run when I start the debugger agent with wait_for_connection enabled (I am not sure if this modification is correct, I have seen on some posts here that there are some issues with the wait_for_connection behavior).
Until now, I was using my own mutex to protect access to isolates, but seems the Locker is doing much more. If I replace my mutex by the v8::Locker, the DebugBreak flag is reseted when I begin locking, I do not really understand why :( I think I really missed something about lockers... Sorry for my newbies interrogations! Le mercredi 12 décembre 2012 12:59:43 UTC+1, Damien Gleizes a écrit : > > Hi all, > > I am trying to implement a remote debugger that connects and receive > message from the debugger agent, just like in d8-debug. > > The agent is started using the v8::Debug::EnableAgent method with wait for > connection enabled. > However when executing some source code, the debugger do not break on > first statement. > > I have several isolates in my application, and never use the default one. > I looked into the code in the v8::Debug::EnableAgent function, and it > seems that it triggers a break if wait_for_connection is true. As no > isolate is given to the v8::Debug::DebugBreak function call, it takes the > default isolate.. but I thought it would take the entered one just like in > the v8::Debug::EnableAgent function. > > I probably missed something... do you think it is the wanted behavior? > Thanks for your help! > > ++Damien. > > > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
