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

"paused on debugger statement" instead of exception in the inspector #21905

Closed
Spown opened this issue Mar 3, 2017 · 3 comments
Closed

"paused on debugger statement" instead of exception in the inspector #21905

Spown opened this issue Mar 3, 2017 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Milestone

Comments

@Spown
Copy link

Spown commented Mar 3, 2017

  • VSCode Version: 1.10.1
  • OS Version: W10x64
  • Node: 6.9.3

Launch config regarding console:

"internalConsoleOptions": "neverOpen"
"console": "externalTerminal"

A simple case of trying to access property of undfined:

Error still passed to debug console:

Shouldn't debugger just show the exception in the inspector on the left in the first place? In my case it just shows the normal local scope, as if it were a breakpoint stop

If I unwrap the lines, it shows that the break happens (at least visibly) one the line prior the one containing the problem:

Regarding "debugger statement" - isn't it too vague?

If I step forward it gets thrown into the external console also, which is probably a correct behavior.

I don't know... some of it may be different issues, some are not even bugs (maybe I'm just used to node2 debugger). Also, it is probably related to #19750

thanx

@isidorn
Copy link
Contributor

isidorn commented Mar 3, 2017

@Spown what debugger are you using. node or node2?

@isidorn isidorn added the info-needed Issue requires more information from poster label Mar 3, 2017
@Spown
Copy link
Author

Spown commented Mar 3, 2017

it looks the same in both node with "protocol": "inspector" and node2

@isidorn isidorn removed the info-needed Issue requires more information from poster label Mar 3, 2017
@roblourens
Copy link
Member

I see the problem, I thought that this was handled through the same path as an exception, but apparently not. Maybe it was in an earlier version of Node.

@roblourens roblourens added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues labels Mar 3, 2017
@roblourens roblourens added this to the March 2017 milestone Mar 3, 2017
@weinand weinand added the verified Verification succeeded label Mar 30, 2017
@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
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants