> > > > From: Ilya Buziuk <[email protected]> > To: "General discussion of project-wide or architectural issues." > > Hi, Ivan > Does the SDBG support V8 remote debugger protocol [1] ? Chrome Remote > Debugger Protocol / WIP protocol is used for front-end debugging, but our > main Neon requirement was Node.js debugger (V8 protocol support is > required). Chromedevtools-Java tooling support both WIP & V8 so it was a > perfect match for us. > > [1] https://github.com/v8/v8/wiki/Debugging%20Protocol > > Good point.
(1) Check here: https://chromium.googlesource.com/external/dart/+/532c5163f199b4b20d641211eeac6dfae2472ce9/dart/editor/tools/plugins/com.google.dart.tools.debug.core/src/com/google/dart/tools/debug/core/server/VmConnection.java Besides the Chrome WIP protocol, the Dart debugger also supported debugging of the standalone Dart VM. Whether the Dart VM debugging protocol has anything to do with the V8 debugging protocol, I honestly don't know, but I might speculate chances are high, because the Dart VM is a creation of Lars Bak, who used to lead the V8 VM... A long shot, I know... *(2) But then - even more importantly - check these:* https://medium.com/@paul_irish/debugging-node-js-nightlies-with-chrome-devtools-7c4a1b95ae27#.zfvv5ia3j https://github.com/nodejs/node/pull/6792 https://github.com/v8/v8/tree/ba41697cbd72ea7dcdd89e6dbe9090ecb156ce6c/src/inspector To me it seems that in the meantime V8 got support for WIP / Chrome debugging protocol, no? According to remotedebug.org, the world seems to unite around the WIP protocol (with Mozilla being the notable exception): http://compatibility.remotedebug.org/ Cheers, I.
_______________________________________________ wtp-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
