Repository navigation
Parse entropy-coded data in jpg example - #311
Merged
Merged
Conversation
The scan data following an SOS segment was parsed as another segment, which yielded a bogus marker and seeked past the end of the file. Read it into a buffer up to the next marker so that following segments, including EOI, are parsed correctly.
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.
The entropy-coded scan data following an SOS segment was parsed as another segment. This yielded a bogus marker (
0xFA89) with a length of 18931 for a 2047-byte file, seeked past the end of the file, and never reached EOI.Read the scan data into a
databuffer up to the next marker (any0xFFxxother than the stuffed0xFF00and the RSTn markers). The segments are now SOI, APP0, APP12, APP14, DQT, SOF2, DHT, 10 × SOS, and EOI.