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.

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

Debugging Issue VS 2022 .net 9 #110841

Closed
claimrevolution opened this issue Dec 19, 2024 · 2 comments
Closed

Debugging Issue VS 2022 .net 9 #110841

claimrevolution opened this issue Dec 19, 2024 · 2 comments

Comments

@claimrevolution
Copy link

Description

Since I upgraded to .net 9 I've noticed a random debugging problem. When stepping over code the debugger will jump to the next break point as if hit continue. It seems to be random but happens more often than not. It feels like I'm running something with async and wait and forgot the await part somewhere, but the code I've been using are standard non parallel calls so there are no asyncs going on.

Reproduction Steps

debug code, put several break points. I recommend iterating through a list then a break point at the start and then several in deeper methods. then start stepping over code in those deep methods. it will magically hit the break point at the start of the loop.

Expected behavior

it should keep stepping over code and not hit the next break point randomly.

Actual behavior

the debugger doesn't all ways step over code and going to the next line. it jumps to the next break point.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Dec 19, 2024
Copy link
Contributor

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

@tommcdon
Copy link
Member

Duplicate to #109785, #109812, #109885

@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Dec 19, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jan 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants