Skip to content
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.

Sign up for GitHub

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

Jump to bottom

After upgrading to .NET 9, simple C# statement triggers fatal error in Visual Studio 2022 when Control-C is used to exit #107263

Closed
vsfeedback opened this issue Sep 2, 2024 · 1 comment · Fixed by #107511
Closed

After upgrading to .NET 9, simple C# statement triggers fatal error in Visual Studio 2022 when Control-C is used to exit #107263

vsfeedback opened this issue Sep 2, 2024 · 1 comment · Fixed by #107511
Assignees
@tommcdon
Labels
area-Diagnostics-coreclr in-pr There is an active PR which will close this issue when it is merged
Milestone
10.0.0

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.

[severity:I'm unable to use this version]
A complete description of the problem, including screenshots and code that triggers the error can be found here:

https://stackoverflow.com/questions/78890260/after-upgrading-to-net-9-simple-c-sharp-statement-triggers-fatal-error-in-visu

Original Comments

Feedback Bot on 8/22/2024, 02:14 AM:

(private comment, text removed)

Tom McDonald [MSFT] on 8/23/2024, 04:20 PM:

(private comment, text removed)

David Sworder on 8/23/2024, 04:28 PM:

(private comment, text removed)

Tom McDonald [MSFT] on 8/26/2024, 10:28 PM:

(private comment, text removed)

David Sworder on 8/27/2024, 05:35 PM:

(private comment, text removed)

Original Solutions

(no solutions)
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Sep 2, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Sep 2, 2024
@tommcdon tommcdon added this to the 10.0.0 milestone Sep 2, 2024
@tommcdon tommcdon self-assigned this Sep 2, 2024
@tommcdon tommcdon removed untriaged New issue has not been triaged by the area owner needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Sep 2, 2024
@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

@tommcdon tommcdon mentioned this issue Sep 8, 2024
Merged
@dotnet-policy-service dotnet-policy-service bot added the in-pr There is an active PR which will close this issue when it is merged label Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tommcdon tommcdon

Labels
area-Diagnostics-coreclr in-pr There is an active PR which will close this issue when it is merged
Projects
None yet
Milestone
10.0.0
Development

Successfully merging a pull request may close this issue.

Avoid using OpenThread for out of process SetThreadContext debugging tommcdon/runtime
2 participants
@tommcdon @vsfeedback