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
Visual Studio has a breakpoint called Dependent Breakpoint.
This is a breakpoint that is only activated when a specific breakpoint is called.
I have noticed that I can reproduce dependent breakpoints by adding a way to get the hit count of the specified breakpoint.
If you want to get the hit counts of other breakpoints in the conditional expression of a breakpoint, use GetMetaVar("hitCount", BREAKPOINT_ID).
However, it seems that it is necessary to think about how to inform the user about the ID of the breakpoint.
In Visual Studio, this could be selected from a combo box in the UI, but there is no such UI in VSCode. My idea is to display the ID in a UI that displays a list of breakpoints. This could be achieved if the labels of the breakpoints could be changed.
The problem is breakpoints that are not displayed on the UI, e.g. debug directives. These have no way to provide the ID to the user.
Visual Studio has a breakpoint called Dependent Breakpoint.
This is a breakpoint that is only activated when a specific breakpoint is called.
I have noticed that I can reproduce dependent breakpoints by adding a way to get the hit count of the specified breakpoint.
If you want to get the hit counts of other breakpoints in the conditional expression of a breakpoint, use
GetMetaVar("hitCount", BREAKPOINT_ID)
.However, it seems that it is necessary to think about how to inform the user about the ID of the breakpoint.
In Visual Studio, this could be selected from a combo box in the UI, but there is no such UI in VSCode. My idea is to display the ID in a UI that displays a list of breakpoints. This could be achieved if the labels of the breakpoints could be changed.
The problem is breakpoints that are not displayed on the UI, e.g. debug directives. These have no way to provide the ID to the user.
Please let me know if there is a better solution.
The following ideas may provide a solution.
The text was updated successfully, but these errors were encountered: