ndb - the node.js debugger Google Group

Re: Debugging on remote machine

odva...@gmail.com (Jan Honza Odvarko) — Wed, 17 Nov 2010 18:36:40 UT

I have found some more info and a solution here:
[link]

The problem is that V8 debugger thread listens only on 127.0.0.1

Honza

Re: Debugging on remote machine

sc...@railsnewbie.com (Scott Taylor) — Tue, 16 Nov 2010 15:16:06 UT

I'd do a head check to make sure that port is actually open:
nmap 10.0.0.2 -p 5858
If it *is* open, then please file a bug report:
[link]
Thanks,
Scott

Re: Debugging on remote machine

odva...@gmail.com (Jan Honza Odvarko) — Mon, 15 Nov 2010 12:32:32 UT

I did use the --host option.

Here is my scenario.

1) I have ran the node process one the first machine (10.0.0.2) as
follows:
$ node --debug-brk main.js
debugger listening on port 5858

2) Consequently I ran the ndb on the second machine:
$ ./bin/ndb --host 10.0.0.2
Could not connect to host 10.0.0.2 on port 5858. Will try again in 2

Re: Debugging on remote machine

sc...@railsnewbie.com (Scott Taylor) — Sat, 13 Nov 2010 23:23:36 UT

Yeah - just use the --host option (see --help for other options like --port if you need them).
HTH,
Scott

Debugging on remote machine

odva...@gmail.com (Jan Honza Odvarko) — Sat, 13 Nov 2010 14:54:33 UT

I can't connect ndb to a node process (launched as $ node --debug
script.js) that is running on a different machine, it works only with
127.0.0.1 host. Is that known limitation or I am rather doing
something wrong?

Honza

[ANN] ndb 0.1.5

sc...@railsnewbie.com (Scott Taylor) — Sun, 30 May 2010 06:19:51 UT

Another point release of ndb, the node.js debugger. From the changelog:
== 0.1.5 / 2010-05-30
* add history tracking
ndb> history
1 list
2 n
3 history
* repl
ndb> repl
Welcome to the ndb repl.
Type .break to exit.
repl> this
=> #<an Object>
repl> 1+1
=> 2
repl> .break

[ANN] ndb 0.1.4 released

sc...@railsnewbie.com (Scott Taylor (smtlaissezfaire)) — Thu, 20 May 2010 05:54:07 UT

Releasing 0.1.4 of ndb. Some new features:

* a --local option (a convenience for running one command instead of
two)
* backtrace functionality implemented.

See the CHANGELOG for more.

[link]
[link]

I've also setup a mailing list for any bug reports, questions, and