I was thinking a good idea would be looking into taking the work done
on ndb and the open source Chrome JS debugger to produce a similar
plugin for Chrome that would remotely debug running Node programs.
I wonder if there is even a hack to integrate Node debugging into the
existing Chrome debugger but a separate plugin would probably be
necessary. Has anyone else had similar thoughts? It doesn't seem
like this would be too far out of reach. The advantages would be:
- Graphical debugging without Eclipse.
- Attracting client-side JS programmers who are used to Firebug style
debuggers to Node.
- Reusing code in the existing Chrome debugger.
--
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com.
To unsubscribe from this group, send email to nodejs+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
> Any news for this projects? Currently, want to debug a remote node
> server (a bug only happen in that machine).
> And found that eclipse debugger only can be used for local node
> server.
> If you can make the node debugged by chrome debugger. Please tell me.
Are you debugging server side remote node.js backend, or a chrome/browser-based front end?
You can debug remote node instances as long as you start them with node --debug (or --debug-brk). See ndb --help and node --help | grep debug.
Scott
Might be simpler to just use the tunnel option of ssh or even ncat.
On Jun 18, 2010 12:08 AM, "Zoka" <ztom...@gmail.com> wrote:
You can debug remote Node app with Eclipse debugger, but you have to
run 2 instances of TCP proxy (tcpproxy.js), one on local machine an
one on the remote. Have look at the
http://wiki.github.com/ry/node/using-eclipse-as-node-applications-debugger
Same proxy arrangement can be used with ndb.
Zoka
On Jun 18, 12:19 pm, Eric Fong <eri...@gmail.com> wrote:
> Any news for this projects? Currently, ...