Avoid std::copy calls that make 0 length copy, possibly reading from an invalid pointer (UBSAN issue) - #1627
Open
perrydv wants to merge 1 commit into
Open
Avoid std::copy calls that make 0 length copy, possibly reading from an invalid pointer (UBSAN issue)#1627perrydv wants to merge 1 commit into
perrydv wants to merge 1 commit into
Conversation
…an invalid pointer (UBSAN issue)
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
1 participant
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.
This attempts to the fix the latest CRAN UBSAN (non-)issue from code that has been working for years.
I'm having a hard time reproducing the original UBSAN issue so I haven't verified that this fixes it, but I think it should. In any case I'll run testing.
The changes are minor so there really shouldn't be a testing problem...