-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Copied from https://github.com/BUS-OGD/jester/blob/old-jester/HACKING.md (commit ee368a2)
- Loading branch information
Oscar de Groot
committed
Jun 25, 2014
1 parent
ab28734
commit bf27283
Showing
1 changed file
with
22 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# How to debug Jester | ||
|
||
You attach a graphical debugger ([node-inspector]) to the unittests, or to the compiled jester.js | ||
|
||
### Attaching the debugger to the compiled jester.js | ||
|
||
1. Start node-inspector on port 8080: | ||
|
||
$ cd <jester source dir> | ||
$ .\dist\node_modules\.bin\node-inspector --web-port=8080 | ||
info - socket.io started | ||
visit http://0.0.0.0:8080/debug?port=5858 to start debugging | ||
|
||
2. Start jester in debug mode: | ||
|
||
$ .\dist\node.exe --debug-brk .\dist\jester.js | ||
debugger listening on port 5858 | ||
|
||
3. Open a browser on http://localhost:8080 | ||
4. place your breakpoints and press the play button to start running jester. | ||
|
||
[node-inspector]: https://npmjs.org/package/node-inspector |