Use segment number from SegmentInfo#420
Merged
makubacki merged 1 commit intoJun 22, 2026
Merged
Conversation
mu-automation
Bot
added
the
impact:non-functional
antklein
approved these changes
Jun 22, 2026
Contributor
|
@makubacki, can we get your help reviewing this change? |
makubacki
approved these changes
Jun 22, 2026
… an invalid access. Signed-off-by: Chris Ruffin <cruffin@millcore.com>
makubacki
force-pushed
the
personal/v-chrruffin/test-point
branch
from
cc571b2 to
0ba0240
Compare
apop5
approved these changes
Jun 22, 2026
Contributor
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Description
The segment index is not always the segment number, which can lead to an invalid access.
How This Was Tested
Unit test on AARCH64 platform.
Integration Instructions
NA