Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Throwing exception on simple use case

See original GitHub issue

First time using node-inspector. Here’s my setup:

$ nvm --version
0.31.4
$ nvm current
v6.4.0
$ node --version
v6.4.0
$ npm install -g node-inspector

My simple test file:

//test.js
var d = {asdf: 123}
debugger;
console.log(d)

Firing up the debugger throws exception:

$ node-debug test.js
Node Inspector v0.12.8
Visit http://127.0.0.1:8080/?port=5858 to start debugging.
Debugging `test.js`

Debugger listening on [::]:5858
/Users/wes/.nvm/versions/node/v6.4.0/lib/node_modules/node-inspector/lib/InjectorClient.js:111
      cb(error, NM[0].ref);
                     ^

TypeError: Cannot read property 'ref' of undefined
    at InjectorClient.<anonymous> (/Users/wes/.nvm/versions/node/v6.4.0/lib/node_modules/node-inspector/lib/InjectorClient.js:111:22)
    at /Users/wes/.nvm/versions/node/v6.4.0/lib/node_modules/node-inspector/lib/DebuggerClient.js:121:7
    at Object.create.processResponse.value (/Users/wes/.nvm/versions/node/v6.4.0/lib/node_modules/node-inspector/lib/callback.js:23:20)
    at Debugger._processResponse (/Users/wes/.nvm/versions/node/v6.4.0/lib/node_modules/node-inspector/lib/debugger.js:95:21)
    at Protocol.execute (_debugger.js:121:14)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:177:18)
    at Socket.Readable.push (_stream_readable.js:135:10)
    at TCP.onread (net.js:542:20)

Issue Analytics

State:
Created 7 years ago
Reactions:88
Comments:62 (1 by maintainers)

Top GitHub Comments

78reactions

timothyerwincommented, Sep 9, 2016

@wzup solution: stop using windows.

52reactions

kmkrcommented, Sep 7, 2016

Those running 6.5.0 can use native node for the same purposes. It’s an experimental feature, but it works fine for me.

node --inspect --debug-brk my-app.js.

Top Results From Across the Web

How to Throw Exceptions in Java - Rollbar

Throwing an exception is as simple as using the "throw" statement. You then specify the Exception object you wish to throw.

Writing Use Cases: Exception or Alternate Flow?

Learn when to describe an exception and when to go into an alternate flow. This is essential to improve readability of your use...

How to Throw Exceptions (The Java™ Tutorials > Essential ...

This Java tutorial describes exceptions, basic input/output, concurrency, regular expressions ... All methods use the throw statement to throw an exception.

Creating and Throwing Exceptions | Microsoft Learn

Exceptions are used to indicate that an error has occurred while running the program. Exception objects that describe an error are created and ......

Throwing an exception in Java - Javamex

To throw an exception, we generally use the throw keyword followed by a newly constructed exception object (exceptions are themselves objects in Java)....