Fixes for reading malformed/truncated PAM files#532
Merged
jonsneyers merged 1 commit intoFLIF-hub:masterfrom Sep 3, 2021
Merged
Fixes for reading malformed/truncated PAM files#532jonsneyers merged 1 commit intoFLIF-hub:masterfrom
jonsneyers merged 1 commit intoFLIF-hub:masterfrom
Conversation
|
Indentation appears to be spaces. |
d11mshepcar
force-pushed
the
fix-pam-reader
branch
from
68f116b to
2485f1b
Compare
Contributor
Author
The formatting is all over the place anyway but I've updated my commit to be in line with surrounding code. |
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
3 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.
I've fixed two problems in the PAM reader relating to reading past EOF and reading pixel values outside of the maximum range. This fixes issue #513