Skip to content

Fix nondeterminism in VALIDATE_AND_RETURN caused by comparing uniniti… #3351

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

Conversation

adrian-prantl
Copy link

…alized values

@adrian-prantl adrian-prantl merged commit b2632c9 into swiftlang:stable/20210726 Oct 5, 2021
Comment on lines +2493 to +2500
child_name = "";
child_byte_size = 0;
child_byte_offset = 0;
child_bitfield_bit_size = 0;
child_bitfield_bit_offset = 0;
child_is_base_class = false;
child_is_deref_of_parent = false;
language_flags = 0;

Choose a reason for hiding this comment

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

Why are these reset here? If this is needed, it's missing a #ifndef NDEBUG

Copy link
Author

Choose a reason for hiding this comment

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

It's because we'll validate them against their ast_* counterparts.
They are initialized unconditionally because the initialization has an effect outside of the function (these are passed in by reference), I really don't want to change LLDB's behavior in asserts/non-asserts build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants