abrown opened PR #4253 from fix-region-sizes
to main
:
When adding shared memory, memories owned by the module were added to a
owned_memories
array placed immediately after thedefined_memories
array. When checking the size of each array withregion_sizes
, the
size ofdefined_memories
andowned_memories
were checked in this
order. Butregion_sizes
is iterating through the fields in the reverse
order. This change reverses the field order to fix the associated fuzz
bug.<!--
Please ensure that the following steps are all taken care of before submitting
the PR.
[ ] This has been discussed in issue #..., or if not, please tell us why
here.[ ] A short description of what this does, why it is needed; if the
description becomes long, the matter should probably be discussed in an issue
first.[ ] This PR contains test cases, if meaningful.
- [ ] A reviewer from the core maintainer team has been assigned for this PR.
If you don't know who could review this, please indicate so. The list of
suggested reviewers on the right can help you.Please ensure all communication adheres to the code of conduct.
-->
abrown requested alexcrichton for a review on PR #4253.
alexcrichton submitted PR review.
alexcrichton merged PR #4253.
Last updated: Nov 22 2024 at 17:03 UTC