0
0
mirror of https://github.com/nodejs/node.git synced 2024-11-29 23:16:30 +01:00
nodejs/doc/api/debugger.markdown

139 lines
3.9 KiB
Markdown
Raw Normal View History

2012-02-27 20:08:17 +01:00
# Debugger
Stability: 3 - Stable
<!-- type=misc -->
2010-12-31 03:46:49 +01:00
2011-02-25 01:36:43 +01:00
V8 comes with an extensive debugger which is accessible out-of-process via a
2010-12-31 03:46:49 +01:00
simple [TCP protocol](http://code.google.com/p/v8/wiki/DebuggerProtocol).
Node has a built-in client for this debugger. To use this, start Node with the
`debug` argument; a prompt will appear:
% node debug myscript.js
2011-09-25 13:10:21 +02:00
< debugger listening on port 5858
connecting... ok
break in /home/indutny/Code/git/indutny/myscript.js:1
1 x = 5;
2 setTimeout(function () {
3 debugger;
2010-12-31 03:46:49 +01:00
debug>
Node's debugger client doesn't support the full range of commands, but
simple step and inspection is possible. By putting the statement `debugger;`
into the source code of your script, you will enable a breakpoint.
For example, suppose `myscript.js` looked like this:
// myscript.js
x = 5;
setTimeout(function () {
debugger;
console.log("world");
}, 1000);
console.log("hello");
Then once the debugger is run, it will break on line 4.
2011-09-25 13:10:21 +02:00
% node debug myscript.js
< debugger listening on port 5858
connecting... ok
break in /home/indutny/Code/git/indutny/myscript.js:1
1 x = 5;
2 setTimeout(function () {
3 debugger;
debug> cont
< hello
break in /home/indutny/Code/git/indutny/myscript.js:3
1 x = 5;
2 setTimeout(function () {
3 debugger;
4 console.log("world");
5 }, 1000);
2010-12-31 03:46:49 +01:00
debug> next
2011-09-25 13:10:21 +02:00
break in /home/indutny/Code/git/indutny/myscript.js:4
2 setTimeout(function () {
3 debugger;
4 console.log("world");
5 }, 1000);
6 console.log("hello");
debug> repl
Press Ctrl + C to leave debug repl
> x
2010-12-31 03:46:49 +01:00
5
2011-09-25 13:10:21 +02:00
> 2+2
2010-12-31 03:46:49 +01:00
4
debug> next
2011-09-25 13:10:21 +02:00
< world
break in /home/indutny/Code/git/indutny/myscript.js:5
3 debugger;
4 console.log("world");
5 }, 1000);
6 console.log("hello");
7
2010-12-31 03:46:49 +01:00
debug> quit
%
2011-09-25 13:10:21 +02:00
The `repl` command allows you to evaluate code remotely. The `next` command
steps over to the next line. There are a few other commands available and more
to come. Type `help` to see others.
2010-12-31 03:46:49 +01:00
2012-02-27 20:08:17 +01:00
## Watchers
You can watch expression and variable values while debugging your code.
On every breakpoint each expression from the watchers list will be evaluated
in the current context and displayed just before the breakpoint's source code
listing.
To start watching an expression, type `watch("my_expression")`. `watchers`
prints the active watchers. To remove a watcher, type
`unwatch("my_expression")`.
2012-02-27 20:08:17 +01:00
## Commands reference
2012-02-27 20:08:17 +01:00
### Stepping
* `cont`, `c` - Continue execution
* `next`, `n` - Step next
* `step`, `s` - Step in
* `out`, `o` - Step out
* `pause` - Pause running code (like pause button in Developer TOols)
2012-02-27 20:08:17 +01:00
### Breakpoints
* `setBreakpoint()`, `sb()` - Set breakpoint on current line
* `setBreakpoint(line)`, `sb(line)` - Set breakpoint on specific line
* `setBreakpoint('fn()')`, `sb(...)` - Set breakpoint on a first statement in
functions body
* `setBreakpoint('script.js', 1)`, `sb(...)` - Set breakpoint on first line of
script.js
* `clearBreakpoint`, `cb(...)` - Clear breakpoint
2012-02-27 20:08:17 +01:00
### Info
* `backtrace`, `bt` - Print backtrace of current execution frame
* `list(5)` - List scripts source code with 5 line context (5 lines before and
after)
* `watch(expr)` - Add expression to watch list
* `unwatch(expr)` - Remove expression from watch list
* `watchers` - List all watchers and their values (automatically listed on each
breakpoint)
* `repl` - Open debugger's repl for evaluation in debugging script's context
2012-02-27 20:08:17 +01:00
### Execution control
* `run` - Run script (automatically runs on debugger's start)
* `restart` - Restart script
* `kill` - Kill script
2012-02-27 20:08:17 +01:00
### Various
* `scripts` - List all loaded scripts
* `version` - Display v8's version
2010-12-31 03:46:49 +01:00
2012-02-27 20:08:17 +01:00
## Advanced Usage
2010-12-31 03:46:49 +01:00
The V8 debugger can be enabled and accessed either by starting Node with
the `--debug` command-line flag or by signaling an existing Node process
with `SIGUSR1`.