Fix header parsing for 64-bit CPUs #5
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 had trouble parsing some table headers (the fields would come out garbled or empty), and after finding a note from the original author that a 32-build should be used and confirming that helps I traced it to this single variable that is used for it's "sizeof" to advance the file pointer.
Making sure it's always 4 bytes helped. The actual value isn't used, as far as I can tell, but I didn't want to change more than needed.