microsoft / microsoft/MIEngine
VS IDE: A breakpoint that is set but disabled in design mode will appear bound in run mode but not be hit.
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
This repros in VS IDE for MIEngine against both gdb and clrdbg.
Repro:
- File -> New Project -> Visual C++ -> Cross Platform -> Android -> Native ActivityApplication
- Set a breakpoint in android_main but disable it:
- F5
Expected: Breakpoint exists but appears disabled and is not hit
Actual: Breakpoint appears bound but does not get hit:
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
Reproduce the issue in the VS IDE using MIEngine with both gdb and clrdbg, following the Android Native ActivityApplication steps and the disabled breakpoint on android_main. Compare breakpoint state before and after F5. Done means the breakpoint remains visibly disabled, appears unbound as appropriate, and is not hit in run mode.
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
- 32/100