Fix CORDBG_E_MODULE_NOT_LOADED error in func-eval

[tommcdon]

Correctly initialize vmModule in FuncEvalComplete in the debugger
Fixes #120848

[Copilot]

Pull Request Overview

This PR fixes a CORDBG_E_MODULE_NOT_LOADED error in the debugger's function evaluation by ensuring the vmModule field is properly initialized to NULL in TypeHandleToBasicTypeInfo. The fix addresses issue #120848 where uninitialized vmModule pointers could cause errors during debugging operations.

Key changes:

• Added initialization of res->vmModule.SetRawPtr(NULL) in three code paths within the switch statement

[dotnet-policy-service]

Tagging subscribers to this area: @steveisok, @dotnet/dotnet-diag
See info in area-owners.md if you want to be subscribed.

[hoyosjs]

/backport to release/10.0

[github-actions]

Started backporting to release/10.0 (link to workflow run)

[AaronRobinsonMSFT]

@tommcdon Was this a long standing issue or was this introduced with a new feature/PR?

[tommcdon]

@tommcdon Was this a long standing issue or was this introduced with a new feature/PR?

@AaronRobinsonMSFT #118414 exposed a latent issue where we didn't zero init the debugger reponse for func-eval. t's access non-initialized memory and so the value is random. On x86 this seems to happen relatively consistently in the test case we used to investigate. While the issue was found on x86 func-eval testing, the issue could happen on any architecture.