microsoft / microsoft/MIEngine
There is no way to disable a one of the BoundBreakpoint when there is more than one binding
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
When one PendingBreakpoint corresponds to more than than one BoundBreakpoints, it's possible to disable only some of the BoundBreakpoints from Visual Studio debugger UI, but MIEngine simply ignores the disable/enable operation. IDebugBoundBreakpoint2.Enable should use MI commands like "=break-disable 2.1" to disable the corresponding BoundBreakpoint.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the IDebugBoundBreakpoint2.Enable implementation and trace how a PendingBreakpoint with multiple BoundBreakpoints handles enable and disable requests. Verify the MI command mapping for an individual binding, such as =break-disable 2.1, and consider the corresponding enable operation; done means Visual Studio can toggle one bound breakpoint without affecting its siblings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100