It would have to peek at the packets, and somehow figure out that the attach is really just a ping, and respond to that ping itself without spinning up Node. Right now it's just a dumb pipe that copies packets over from an externally visible socket to the one that Node actually binds to. To fix this, we'll need to make the proxy smarter. It immediately detaches after receiving the initial V8 response, but it still counts as an attach, so the proxy spins up the actual process. Node starts running when I press Attach buttonĬomments: This is an unfortunate side effect of the Attach to Process dialog actually doing the attach when populating the process list, to make sure that the machine has Node running on that port. ![]() After setting the Node.js transport, enter the appropriate qualifier On remote target run the command: "Node.exe RemoteDebug.js -waitforattach "ģ.
0 Comments
Leave a Reply. |