Hi,
i have successfully integrated remote debugging through chrome dev tools to
an embedded v8 in an android app.
I can see v8's loaded source code, do profiling, memory dumps, etc., but JS
debugging is not working as expected.
Whenever the debugger hits a breakpoint, the session channel sends a
`{"method":"Debugger.paused"...` message to dev tools frontend.
After that, InspectorClient has its method `runMessageLoopOnPause` called
from V8Debugger, and here is where things don't fully work on my side.
The JS execution gets only stopped if I don't exit `runMessageLoopOnPause`
method. Otherwise, I would get some debugger information, like evaluated
variables values, but the javascript execution is not stopped.
My project is quite complex, where several different operations are wired
to javascript, like touch or timers.
I assume all external js calls should be disabled while running
`runMessageLoopOnPause`, maybe until `quitMessageLoopOnPause` is called ?.
However, this is just guessing. For a simpler example, where just some
javascript is compiled and run, w/o threading or external stuff working,
remote debugger works just fine.
Could anyone point me to a place where i could read about what i am
supposed to do on these methods ? Any hints on how to handle debugger
interaction at this point would be highly appreciated.
Thanks.
--
--
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.
