Skip to content

[mono] Fix use of uninitialized variable #117140

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

Merged
merged 1 commit into from
Jun 30, 2025
Merged

Conversation

BrzVlad
Copy link
Member

@BrzVlad BrzVlad commented Jun 30, 2025

Unlikely for this to fix an issue, but should prevent false positives with valgrind. Use added in #73786

Unlikely for this to fix an issue, but should prevent false positives with valgrind.
@Copilot Copilot AI review requested due to automatic review settings June 30, 2025 06:20
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR fixes a potential uninitialized variable issue in the mono runtime by explicitly setting interface_offsets_full to zero when bitmap_only is true.

  • Introduces a branch to initialize interface_offsets_full in the bitmap_only scenario.
  • Prevents false positives with valgrind by ensuring consistent initialization in mono_class_setup_interface_offsets_internal.

@BrzVlad
Copy link
Member Author

BrzVlad commented Jun 30, 2025

cc @lambdageek

@lewing lewing merged commit d3332d4 into dotnet:main Jun 30, 2025
64 of 70 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants