Recent changes to ChromeDevToolsProtocol

Discussion for ChromeDevToolsProtocol page

Anonymous — Sat, 25 Apr 2015 13:43:40 -0000

Originally posted by: alexchan...@gmail.com

{"command":"debugger_command","data":{"seq":100,"type":"request","command":"version"}}

Discussion for ChromeDevToolsProtocol page

Anonymous — Sat, 25 Apr 2015 13:43:40 -0000

Originally posted by: peter.ry...@gmail.com

Hi Elias,

let's have this talk in a dedicated place: http://groups.google.com/group/chromedevtools-dev (I'll need to join it first I believe.) This is not a right place for such discussions.

Peter

Discussion for ChromeDevToolsProtocol page

Anonymous — Sat, 25 Apr 2015 13:43:40 -0000

Originally posted by: elias.po...@gmail.com

Some more info, the actual socket string I am sending is:

Tool:V8Debugger? Destination:2 Content-Length:86

{"command":"debugger_command","data":{"seq":100,"type":"request","command":"version"}}

Discussion for ChromeDevToolsProtocol page

Anonymous — Sat, 25 Apr 2015 13:43:40 -0000

Originally posted by: elias.po...@gmail.com

Hi, I opended a TCP/IP socket with telnet semantics, handshaked ok, attached ok, and now I am trying to send some more complex commands. I am stuck even though I am using the syntax as eclipse plugin. How do I send a simple version command?

This is what I use:

{"command":"debugger_command","data":{"seq":100,"type":"request","command":"version"}}

Elias

Discussion for ChromeDevToolsProtocol page

Anonymous — Sat, 25 Apr 2015 13:43:40 -0000

Originally posted by: splinete...@gmail.com

Thanks I'll check eclipse and continue this discussion in the group Cheers Dan

Discussion for ChromeDevToolsProtocol page

Anonymous — Sat, 25 Apr 2015 13:43:40 -0000

Originally posted by: peter.ry...@gmail.com

Daniel

If you need you always can spy on the current protocol right from the Eclipse IDE. You just have to enable "Show debugger network communication console" in debug launch configuration.

As to the new protocol -- yes, you found its reference. Unfortunately the announce is not here yet, so you'll have to wait for it to learn the details. New protocol won't work via the old transport protocol (DevToolsService?).

I suggest we move further discussion into chromedevtools-dev group, which is better for this.

Peter

Discussion for ChromeDevToolsProtocol page

Anonymous — Sat, 25 Apr 2015 13:43:40 -0000

Originally posted by: splinete...@gmail.com

Thanks! Please keep it posted, I'll update my code as you guys update yours, no problem. I am very serious about adding support of google chrome to my debugger. I believe in it. And this wire protocol is very simple way to do it. All I need is 1 complete sample JSON command with header per "supported tool" and a list of commands, and I will just plug it all into an already functioning debugger. It's not that complicated. I think Google will only win if my debugger supports it.

I sent a request to join the group.

I saw a list of command in Remote-debugging section here: http://code.google.com/chrome/devtools/docs/remote-debugging.html May be you are referring to it.

They look interesting. They don't work if I run them under DevToolsService?. How can I run any one of them?

Cheers

Daniel www.remotedebugger.com

Discussion for ChromeDevToolsProtocol page

Anonymous — Sat, 25 Apr 2015 13:43:40 -0000

Originally posted by: peter.ry...@gmail.com

Hi Daniel

Good luck with your debugger! Should you have any questions about protocol stuff feel free to contact our http://groups.google.com/group/chromedevtools-dev group.

Also probably I should mention our recent plans on switching to a new protocol (known as WebInspector? protocol). This wiki page will be updated soon once I have a document to refer.

Peter

Discussion for ChromeDevToolsProtocol page

Anonymous — Sat, 25 Apr 2015 13:43:40 -0000

Originally posted by: splinete...@gmail.com

I found a way: Content-Length:22 Tool:DevToolsService?

{"command": "version"}

Soon google fans will have a new commercial debugger

Daniel www.remotedebugger.com

Discussion for ChromeDevToolsProtocol page

Anonymous — Sat, 25 Apr 2015 13:43:40 -0000

Originally posted by: splinete...@gmail.com

After successful handshake, which felt great, I send this and it gets ignored by chrome. Could you tell me how exactly should this request look like:

Content-Length:18 Tool:DevToolService?

{command:version}

I tried with and without quotes but nothing works. I encode with UTF8 using C# terminal I wrote. The handshake worked though. I am making my debugger support Chrome: www.remotedebugger.com