Fix breakpoint verification UI for the multi session case #40158
Labels
debt
Code quality issues
debug
Debug viewlet, configurations, breakpoints, adapter issues
feature-request
Request for new features or functionality
on-testplan
release-notes
Release notes issues
Milestone
Problem:
If two (or more) concurrent debug sessions return differing verification status for a (shared) breakpoint, then the outcome in the UI is not clear, e.g. we show the verification error for the breakpoint but he breakpoint actually verified fine in one of the sessions. This should not affect the ability to hit a verified breakpoint and miss an unverified breakpoint.
3 Possible solutions:
Today VS Code uses approach 3 but we should strive for solution 2.
In addition we should clarify/improve the DAP in order to support a "don't care" verification status.
The text was updated successfully, but these errors were encountered: