…ent frame when evaluating dynamic expressions in V8
… and made NodeSocket a proper EventEmitter. No more dependency on pilot and ACE, all util functions used now reside in util.js
…nt would simply see frozen debugger controls. The issue occured was: On the server side, the following happens in parallel: * A node process is executed with debugger flags * (after waiting for 100msec) a debugger proxy is created and set to connect to the debugger. The problem is that sometimes the 100msec wait is not enough (why using a fixed timeout?) So, this 100msec wait is bad because: * It slows down the server response on fast machines. * It is not sufficient on slow machines (or machines that are temporarily slow) This was solved by implementing a retry-to-connect in the software that connects to the debugger. Also, upon failure in connecting to the debugger no message was sent back to the client. This has been fixed as well. note: these changes must go along with corresponding changes in cloud9 repository. lib/v8debug/NodeSocket.js: - implemented connect-retry mechanism. It works by first trying to connect without any timeout. If that fails that repeated connection attemps are perform, with timeout interval between them. This goes on until all retry attemps has been made (according to a count value). If error still remains, it is sent to the onend handler.