Address scan-build warning of tmp->tm_mon again #1206
Merged
Conversation
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
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.
Followup to #1178 and #1201. Upon further inspection, it seems like the analyzer fails to realize the subscripts of
ipis indexing the array elements ofmon_lengths(length ofMONSPERYEAR), mistakening the length of the array pointed to byipto be 2 (length ofmon_lengthsinstead ofmon_lengths[n]). To aid scan-build in its analysis, propose changing the type ofipto be explicitly a pointer to arrays of lengthMONSPERYEAR.