Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node debugger stalls when using util.inspect #2753

Closed
benquarmby opened this issue Feb 6, 2016 · 2 comments
Closed

Node debugger stalls when using util.inspect #2753

benquarmby opened this issue Feb 6, 2016 · 2 comments
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@benquarmby
Copy link

Debugging a Node program that uses util.inspect hangs the underlying node process.

I stumbled across this while working on an app that depends on the Azure Storage SDK for Node (it uses util.inspect). I don't have a workaround for debugging right now, but the app works fine when running directly from the command line.

I've created a repro of the problem here:
https://gist.github.com/benquarmby/36f6c00947ad04509212

Steps:

  • Create a script that invokes util.inspect on an object
  • Place a breakpoint in the script after the call util.inspect
  • Start debugging
  • Observe that the breakpoint is not hit

Environment:

  • VSCode 0.10.6
  • Windows 10 x64
  • Node 5.5 x64
@weinand weinand added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) and removed bug Issue identified by VS Code Team member as probable bug labels Feb 8, 2016
@weinand
Copy link
Contributor

weinand commented Feb 10, 2016

@benquarmby I could reproduce the same behaviour with node-inspector, so this is not a VS Code problem but a node problem, most likely a duplicate of nodejs/node#4917.

It does not occur with node version < 4.2.6

@weinand weinand closed this as completed Feb 10, 2016
@benquarmby
Copy link
Author

Right you are. I notice Node JS Tools for Visual Studio repros this bug also. Definitely a node problem and not VS Code specific.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants