microsoft / microsoft/MIEngine
Start debugging with a disabled breakpoint breaks the debugger.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
If debugging is started with a breakpoint set but disabled, it looks like we hang. It is important that the breakpoint is set on a line where it would get hit, but is disabled when debugging is started. Async break no longer works and the debugger is hung.
I am guessing that the breakpoint gets set and hit by gdb, but MIEngine does not understand it.
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 by reproducing the issue with a breakpoint on a line that will be hit, leaving it disabled when debugging starts. Inspect how MIEngine handles the breakpoint reported by gdb and verify that async break resumes instead of leaving the debugger hung.
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