[release/10.0] Fix CORDBG_E_MODULE_NOT_LOADED error in func-eval#121087
Merged
steveisok merged 2 commits intorelease/10.0from Nov 10, 2025
Merged
[release/10.0] Fix CORDBG_E_MODULE_NOT_LOADED error in func-eval#121087steveisok merged 2 commits intorelease/10.0from
steveisok merged 2 commits intorelease/10.0from
Conversation
Contributor
|
Tagging subscribers to this area: @steveisok, @dotnet/dotnet-diag |
noahfalk
approved these changes
Oct 26, 2025
steveisok
added
Servicing-approved
This was referenced Nov 5, 2025
Open
Member
|
/ba-g Known issues #114924 dotnet/dnceng#3008 dotnet/dnceng#5015 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #121057 to release/10.0
/cc @hoyosjs @tommcdon
Customer Impact
Regression found by Visual Studio debugger testing found in .NET 10 RC2
Regression
#118414 exposed latent variable initialization issue in debugger
Testing
Found by Visual Studio debugger testing
Risk
Low - the fix is to zero initialize a variable that is used by the debugger