Roaring64Map::readSafe: Check against maxbytes to read the size of the map #384
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.
Previously, readSafe did not check whether it could read the map size in the allotted maxbytes. In addition, it did not subtract the map size from maxbytes when reading.
This fixes the above and adds some deserialization tests using binary files. The valid files were produced with the script in tests/cpp_unit_util.cpp. The invalid files were created manually.