https://github.com/trepan-debuggers/trepan-ni
A more gdb-like (v8) node-inspect (v8), in the trepan debugger family
https://github.com/trepan-debuggers/trepan-ni
debugger nodejs
Last synced: 8 months ago
JSON representation
A more gdb-like (v8) node-inspect (v8), in the trepan debugger family
- Host: GitHub
- URL: https://github.com/trepan-debuggers/trepan-ni
- Owner: Trepan-Debuggers
- License: mit
- Created: 2018-09-20T21:40:15.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2024-01-09T21:59:17.000Z (over 2 years ago)
- Last Synced: 2025-03-27T11:13:37.309Z (over 1 year ago)
- Topics: debugger, nodejs
- Language: JavaScript
- Homepage:
- Size: 1.4 MB
- Stars: 10
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Governance: GOVERNANCE.md
Awesome Lists containing this project
README
# trepan-ni
A gdb-like debugger in the trepan debugger family.
This guts of this code is based on (and largely made up of) the nodejs
"node inspect" debugger. However the command-line interface is being
expanded and completely reworked.
For example, we include frame-changing _gdb_ commands like `up`,
`down`, and `frame`.
We also document better the in the help system command syntax, and
what each does. See for example `help "break"`. and `help "syntax"`.
For an Emacs interface into this debugger, see
[realgud-trepan-ni](https://github.com/realgud/realgud-trepan-ni).
This is part of the [realgud](https://github.com/realgud/realgud)
debugger interface suite.
## Setup:
```bash
$ npm install
```
## Install from NPM
```bash
$ npm install trepan-ni
```
## Run
```
Usage: trepan-ni [--inspect] # debugs
trepan-ni -p # debugs connecting to
trepan-ni : # debugs connecting to :
```
In the first form, you give a nodejs program to bug. Option
`--inspect` causes the debugger not to stop initially. Otherwise there
is a breakpoint set before the program proper is run.
In contrast to the first form, in the second form it is also presumed
that some nodejs program is already running in debug mode on the same
machine, and the process id, or "pid" for that program is _pid_.
In the the third form, like the second form, it is presumed that some
program is running in debug mode which is available by connecting via
a socket to _host_ at port _port_. This allows you to debug remotely
to a machine or device outside of the one you are debugging from,
although _host_ does not have to be a different machine. For example:
In terminal 1:
```console
$ node --inspect sleep.js
Debugger listening on ws://127.0.0.1:9229/c4f8676e-79dc-453a-8f2b-45d7af9d8327
For help see https://nodejs.org/en/docs/inspector
```
In terminal 2:
```console
$ trepan-ni 127.0.0.1:9229
connecting to 127.0.0.1:9229 ... ok(trepan-ni) pause
(trepan-ni) break in sleep.js:3
1 (function (exports, require, module, __filename, __dirname) { for (let i=1; i<10000; i++) {
2 for (let j=1; j<1000; j++) {
-> 3 for (let k=1; k<10000; k++) {
4 ;
5 }
```
See also the help given by `node --help`, as many of those options are
relevant and accepted. Also note in particular the environment
variables that can be used to influence execution.
See [the demos folder](https://github.com/rocky/trepan-ni/tree/master/demo) for a demonstration of the above and possibly other demos.
#### References
* [Debugger Documentation](https://nodejs.org/api/debugger.html)
* [EPS: `node inspect` CLI debugger](https://github.com/nodejs/node-eps/pull/42)
* [Debugger Protocol Viewer](https://chromedevtools.github.io/debugger-protocol-viewer/)
* [Command Line API](https://developers.google.com/web/tools/chrome-devtools/debug/command-line/command-line-reference?hl=en)