You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently started using the editor widget in an application based on blessed. Now I noticed that I can't debug properly anymore - as soon as the debugger is attached, the screen is plastered with messages like this (strangely enough, debugging seems to work fine while this happens).
Starting inspector on 127.0.0.1:9229 failed: address already in use
The port varies - if I start the debugger from VS Code, it assigns a new random port every time, and the message remains the same with the exception of the port. Using the Node debugger in Chrome shows the same problem though, this is not a VS Code issue.
Tests showed me that my application debugs just fine if I replace the line where I call new Editor(...) with blessed.box(...). I may go and read source code to figure out what it is that the editor widget does that breaks debugging - meanwhile, any ideas from those who know the project?
The text was updated successfully, but these errors were encountered:
oliversturm
added a commit
to oliversturm/editor-widget
that referenced
this issue
Jul 3, 2018
Current node versions don't accept `--debug` and `--debug-brk` anymore without complaints, and current version debuggers pass `--inspect` and `--inspect-brk` anyway. The change solves the problem reported in slap-editor#242, but I have not tested the functionality that was presumably intended by the original author.
I recently started using the editor widget in an application based on blessed. Now I noticed that I can't debug properly anymore - as soon as the debugger is attached, the screen is plastered with messages like this (strangely enough, debugging seems to work fine while this happens).
The port varies - if I start the debugger from VS Code, it assigns a new random port every time, and the message remains the same with the exception of the port. Using the Node debugger in Chrome shows the same problem though, this is not a VS Code issue.
Tests showed me that my application debugs just fine if I replace the line where I call
new Editor(...)
withblessed.box(...)
. I may go and read source code to figure out what it is that the editor widget does that breaks debugging - meanwhile, any ideas from those who know the project?The text was updated successfully, but these errors were encountered: