-
Notifications
You must be signed in to change notification settings - Fork 677
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] Async Break broken due to incorrect Thread Event behavior. #1105
Comments
chuckries
changed the title
[Debugger] Need to send respond to threads request or send Thread Event after attaching
[Debugger] Async Break broken due to incorrect Thread Event behavior.
Jan 5, 2017
It looks like if we are not stopped, OpenDebugAD7 always returns empty threads. |
Additionally, in the case of attach it looks like we don't ever send a Thread Event:
|
gregg-miskelly
added a commit
to gregg-miskelly/vscode-csharp
that referenced
this issue
Jan 20, 2017
This updates the debugger to 1-7-0. This version of the debugger contains a fix for dotnet#1107 and dotnet#1105.
gregg-miskelly
added a commit
that referenced
this issue
Jan 21, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We thought this was a VS Code issue but they are marking it by design.
Steps to reproduce
Expected behavior
Debugger stops
Actual behavior
Nothing Happens
Here is a comment explaining VS Code's behavior. We respond to the initial 'threads' request after configurationDone with no threads, which I believe is correct in our case. Later, we fire a Thread Event when our main thread is created. The issue appears to be that after the Thread Event, the 'threads' request is sent again and we respond with null.
Sample Log:
The text was updated successfully, but these errors were encountered: