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
wesrupert opened this issue
Mar 8, 2017
· 3 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Create a sample C# app with multiple code blocks on the same line:
Set multiple column breakpoints on the line while not debugging
F5 the app
Results:
Expected: setBreakpoints request has multiple breakpoints on the same line
Actual: setBreakpoints request only has the first breakpoint from that line, causing the remaining ones to disappear once the debugger sends a response
Note: Column breakpoint support for the C# extension is in-progress, so the response will not be the same in the wild. The important part is the setBreakpoint command.
@wesrupert great catch - we should have caught this in the endgame. It will be available in tomorrow's insiders.
We also recommend all our debug extension writers to use vscode insiders to faster spot bugs and get on fixes earlier.
isidorn
added
the
bug
Issue identified by VS Code Team member as probable bug
label
Mar 10, 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
Steps to Reproduce:
Create a sample C# app with multiple code blocks on the same line:
Set multiple column breakpoints on the line while not debugging
F5 the app
Results:
Expected: setBreakpoints request has multiple breakpoints on the same line
Actual: setBreakpoints request only has the first breakpoint from that line, causing the remaining ones to disappear once the debugger sends a response
Sample
sample - repro.zip
Debug protocol log from C# debugger:
The text was updated successfully, but these errors were encountered: