where to start on implementing chrome debug-ability for a embedded v8 application?

[Zac Hansen]

I want to be able to debug the code running in my program, and in a previous thread, I was informed that there is currently no way to do this with over the network.

Someone mentioned that this will be (re)added eventually, but when I asked for an estimate of a half-year that might happen, I got no response.

So, if i want to go about it myself, can I get some resources and maybe some hints as to how to start?

I see this page here:

https://developer.chrome.com/devtools/docs/debugger-protocol

and the "tip of tree" protocol page:

https://cs.chromium.org/#chromium/src/third_party/WebKit/Source/devtools/protocol.json&q=protocol.json&sq=package:chromium&type=cs

but I was hoping maybe someone could tell me a minimum set of options I could implement that would give me a proof of concept, or maybe some general breakdown of what the fields in the json mean?  https://chromium.googlesource.com/v8/v8/+/master/src/inspector/js_protocol.json

Any help getting started down the right path would be awesome.   

Thank you.

--Zac

[Zac Hansen]

Or even just confirmation that I'm looking at the right thing to do what I want.  

--
--
v8-users mailing list
v8-u...@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to a topic in the Google Groups "v8-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/v8-users/k8-aZ6C7iMs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to v8-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.