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
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
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
The text was updated successfully, but these errors were encountered:
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
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Mar 3, 2017
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Launch config regarding console:
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
The text was updated successfully, but these errors were encountered: