Embedded V8 and CDP

[Dustin Breese]

I'm embedding V8 into Android application and attempting to get debugger to work.

I'm able to connect via chrome://inspect and initiate a session. I see protocol monitor showing messages. However, sometimes things just get stuck in Pending status and V8 is not returning a response.

I can't find much documentation on it, so I'm just floundering around trying to get the session set up properly. When Chrome connects to the debug server, I see that it sends a slurry of messages such as Runtime.enable, Debugger.enable, etc. Even though I've specified my version as 'v8' or 'node' (not 1.3 or tot), I seem to get the same messages from Chrome no matter what. I am only supporting the ones shown for CDP shown at https://chromedevtools.github.io/devtools-protocol/v8/ and respond to Chrome with an error message for the unsupported Domains and methods.

The main issue I have is that I am not sure why V8 just stops responding to messages. Sometimes when typing in the console in Chrome, I see a Runtime.compileScript and Runtime.evaluate, but often times the message is just stuck in "Pending" status.

Any pointers on what I should try and how to debug this?

Thanks for any direction!

[Yang Guo]

Maybe you can take inspiration in how the inspector is embedded in d8 or inspector-test. It sounds like the way you embed V8 does not run the message loop to handle incoming CDP commands. Hope that helps.

 

Cheers,

Yang

--
You received this message because you are subscribed to the Google Groups "chrome-debugging-protocol" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-debugging-p...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/chrome-debugging-protocol/fddaf559-6c9d-4a65-8c09-d814f60714a8n%40googlegroups.com.