As of 0.30.6, if I start node-inspector, then open the debug page in Chrome
(http://127.0.0.1:8080/?ws=127.0.0.1:8080&port=5858) then run my app with
--debug=5858, the app says "Debugger listening on port 5858" but NOTHING
else happens, the app does not run.

If you reload the Chrome debug page whilst it's sitting doing nothing, you
get this error

E:\dropbox~work\webstorm\usl\livedeploy\windows>electron --debug=5858

E:\dropbox~work\webstorm\usl\livedeploy\windows>Debugger listening on port
5858

events.js:141
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at exports._errnoException (util.js:814:11)
at TCP.onread (net.js:541:26)

Not sure if that's related or not???

On 26 August 2015 at 16:56, Cameron Little notifications@github.com wrote:

I'm in the same position as @shrewdlogarithm
https://github.com/shrewdlogarithm I think, but on OS X 10.10.5.
Running my app with either the --debug-brk or --debug flag doesn't do
anything, no app opening, no activity in the debugger, no error messages.
Without flags, the app opens fine.

—
Reply to this email directly or view it on GitHub
#2335 (comment).

--debug-brk doesn't work #2335

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions