microsoft / microsoft/MIEngine
Console output stops after a few minutes
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
vsdbg: 16.8.11013.1 commit:4b0f186e434a6a8e833baeddc7bd2fad8dd08f41
VS: 2019 16.8.0 Preview 6.0
.NET 5 RC 2
I'm debugging a .NET Core app on a Raspi with ARM32, based on the offroad debugging instructions.
Oddly, after a few minutes, VS no longer shows new debug output. The process continues to run, and I can continue to set new breakpoints, which it will pause on (so the socket is clearly there), but the output window just stops.
It's not clear if this is related, but VS also shows "internal error in the C# compiler" messages.
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
The payload names no repository files or tests; begin with the offroad debugging instructions and reproduce the issue using VS 2019 16.8 Preview 6, .NET 5 RC 2, vsdbg 16.8.11013.1, and an ARM32 Raspberry Pi. Compare the stopped debug output with breakpoint behavior and the C# compiler errors; done means new debug output continues to appear during the running session.
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
- Needs clarification
- Newbie friendliness
- 35/100