-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible Bug - Conflict between Max Occurrence and Combinations Options #32
Comments
Confirmed that the --occurrence-max works in prior commit |
git diff cd717ca master
|
Not just this. The options --start-at and --stop-at can also no longer be used. Furthermore this if statement is now unconditional and you can no longer have an unlimited amount of character occurrences (which was previously at occur_max==0) Line 915 in d12feb1
This was introduced in d12feb1 There is a simple fix and a pull request already exists (#25). This issue should be resolved when the pr gets merged. |
@jsteube confirmed - functionality degraded until this can be fixed. |
The newer build of maskprocessor requires you to set a value of at least two for max occurrence:
--occurrence-max must be set to at least 2
However, due to this option being required, our --combinations option is now broken:
mp64.bin -1 '?u?d' '?1?1?1?1?1?1?1?1?1?1?1?1' --combinations -r2 --occurrence-max can not be used with --combinations
This was not an issue in earlier versions of maskprocessor.
The text was updated successfully, but these errors were encountered: