b6875ad49b
renamed a few occurances of "web page" to "renderer" renamed a few files that had "browser" in their name to "main-process" note that there are still many occurances of web page.
49 lines
1.2 KiB
Markdown
49 lines
1.2 KiB
Markdown
# Debugging the main process
|
|
|
|
The devtools of browser window can only debug the renderer process scripts.
|
|
(I.e. the web pages.) In order to provide a way to debug the scripts of
|
|
the main process, atom-shell has provided the `--debug` and `--debug-brk`
|
|
switches.
|
|
|
|
## Command line switches
|
|
|
|
### `--debug=[port]`
|
|
|
|
When this switch is used atom-shell would listen for V8 debugger protocol
|
|
messages on `port`, the `port` is `5858` by default.
|
|
|
|
### `--debug-brk=[port]`
|
|
|
|
Like `--debug` but pauses the script on the first line.
|
|
|
|
## Use node-inspector for debugging
|
|
|
|
__Note:__ Atom Shell uses node v0.11.13, which currently doesn't work very well
|
|
with node-inspector, and the main process would crash if you inspect the
|
|
`process` object under node-inspector's console.
|
|
|
|
### 1. Start the [node-inspector][node-inspector] server
|
|
|
|
```bash
|
|
$ node-inspector
|
|
```
|
|
|
|
### 2. Enable debug mode for atom-shell
|
|
|
|
You can either start atom-shell with a debug flag like:
|
|
|
|
```bash
|
|
$ atom-shell --debug=5858 your/app
|
|
```
|
|
|
|
or, to pause your script on the first line:
|
|
|
|
```bash
|
|
$ atom-shell --debug-brk=5858 your/app
|
|
```
|
|
|
|
### 3. Load the debugger UI
|
|
|
|
Open http://127.0.0.1:8080/debug?port=5858 in the Chrome browser.
|
|
|
|
[node-inspector]: https://github.com/node-inspector/node-inspector
|