-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugger: Failed to debug Xunit project when start debugging again #1413
Comments
@GraceDong: Any chance you could provide the OmniSharp log when this happens? You can get it by selecting View- >Output and then choosing "OmniSharp Log" from the top-right corner of the Output pane. |
OK. I'm able to reproduce this on Debian 8. For me, it happens if perform the following task a few times in a row:
Eventually, the debugger seems to get into a weird state and the debugger events never fire. That leaves OmniSharp in a bad state, which results in the "Failed to start debugger: null" message. Below is the content of the .NET Test Log output channel from a reproduction of the issue. Note that there were three successful runs and then the debugger didn't reported that it had started the debugging process on the fourth run.
Here's an OmniSharp log at this point. Note that there are a few successful test debugging sessions and then it gets horked:
|
Fixed with #1417. |
Environment data
dotnet --info
output:VS Code version: v1.11.2
C# Extension version: v1.9.0
Steps to reproduce
test-xunit.zip
Expected behavior
Re-start debugging and the breakpoint should be hit again.
Actual behavior
Pop a error message as following:
Log: log.txt
The text was updated successfully, but these errors were encountered: