Make dumps of type CompleteMemoryDump
trust TotalNumberOfPages
header field instead of just MetadataSize
#28
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 fixes #27
When parsing a
DumpType_t::CompleteMemoryDump
type of dump, it seems that the fieldMetadataSize
field from the RdmpHeader can exceed the actual number ofPfnRange
class entries declared. Since we properly check bounds, it will result in a failure.This PR adds a extra check only for
CompleteMemoryDump
to enforce a strict check of the current number of pages declared and stop parsing when the expected number of pages (declared inFullRdmpHeader.TotalNumberOfPages
) is reached.