New Post: Retrieving javascript line index during execution

Hello!

Hmm, we can't reproduce any issues setting breakpoints from Eclipse. Here's a sample from Eclipse's debugger network console:

> Sent to Chrome:
Content-Length:132

{"seq":7,"type":"request","command":"setbreakpoint","arguments":{"line":19,"column":0,"type":"scriptId","enabled":true,"target":58}}
> end of message

> Received from Chrome:
Content-Length:247

{"seq":7,"request_seq":7,"type":"response","command":"setbreakpoint","success":true,"body":{"type":"scriptId","breakpoint":1,"script_id":58,"line":19,"column":0,"actual_locations":[{"line":19,"column":36,"script_id":58}]},"refs":[],"running":true}
> end of message

ClearScript 5.4.1 is paired with a much newer V8 version (3.30 vs. 3.26. The removal of V8's built-in debug agent is the main reason why ClearScript was stuck using a relatively old version for a while. So while the protocol may have changed, perhaps inadvertently, it's more likely that there's some subtle difference between Eclipse's requests and yours.

Can you verify that the requests you're sending are well-formed and have correct content length headers?