microsoft / microsoft/MIEngine
Cannot debug core files in VS when using Local debug options
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
Using appropriate gdb commands in local launch options the MIEngine can be made to load a core file. But gdb never generates anything that looks like a stopping event, so the MIEngine never raises the event to the UI. Suggest that LaunchCompleteCommand.Core is added to generate such an event.
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 tracing the local launch options and the LaunchCompleteCommand.Core path in MIEngine, then inspect how gdb output becomes stopping events for the UI. Confirm the core-file launch behavior and identify the event expected by the UI; done means debugging a core file through local options reaches a stopping state.
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