The debugger is not responding with a payload message when I send a V8 protocol command

152 views
Skip to first unread message

Gabriel Petrovay

unread,
May 21, 2013, 5:57:48 AM5/21/13
to nod...@googlegroups.com
As I detailed in this issue: https://github.com/joyent/node/issues/5512

the V8 debugger does not respond with a body (or it hangs somewhere).

Any ideas why?

Miroslav Bajtoš

unread,
May 22, 2013, 1:36:32 AM5/22/13
to nod...@googlegroups.com
V8 debugger protocol is not HTTP where a request is immediately responded. It works asynchronously instead - you send some messages to V8, V8 send some other messages back, there are usual more messages from V8 than the requests sent.

Now why are you not seeing the response you are expecting? The first thing V8 does upon accepting a new connection is to send back a "connect" message with no payload, which is what curl is showing. Response to your request would be the second message coming from V8, if there was such a thing as two responses for a single request in HTTP.

I would recommend you to either use telnet instead of curl (don't forget to compute content-length of your messages) or use an existing debugger client, e.g. https://github.com/dannycoates/node-inspector/blob/master/lib/debugger.js

Miroslav
Reply all
Reply to author
Forward
0 new messages