bruteforce-crc.cc: Fix errors with initial
& example implementation
#6
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.
Fixes #4. Fixes #5.
Since
initial
was declared to beuint32_t
, the conversion of theargument should likewise be converted to
uint32_t
.size_t
convertsit to 8-bytes, which will not fit into 4-bytes.
probe_initial
should be set to false by default to prevent thecurrent bug. The current bug causes the program to ignore the user
specified value
--initial x
and bruteforce crc seeds.The extra byte output is a typical fence post problem. Fixed with
this PR.
Signed-off-by: Solomon Tan solomonbstoner@yahoo.com.au