Address Sanitizer Issue, Fix Stack buffer reference after it has gone… #3034
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.
Address Sanitizer Issue, Fix Stack buffer reference after it has gone out of scope.
The stack variable object
mh
after call torecvmsg
will reference data contained in the stack buffermh_crtl_buf
. This data is then referenced by a later call togetTargetAddress(mh)
, but the stack buffer has already gone out of scope. This PR moves the stack variable outside of the conditional block scope so that it is still in scope while it is being referenced later on in this method.Issue uncovered by using the CLANG Address Sanitizer.