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.
The current
ql_afl_fuzz
wrapper in Qiling supports setting exit addresses using theexits
parameter. It sets the exit addresses at the start and calls theql_afl_fuzz_custom
wrapper with a dummy fuzz callback.Although both
ql_afl_fuzz
andql_afl_fuzz_custom
wrappers have almost the same API, it is impossible to set exit addresses ifql_afl_fuzz_custom
is called directly.To address this issue, I passed the exits parameter seamlessly to
ql_afl_fuzz_custom
for both wrappers to support setting exit addresses.Checklist
Which kind of PR do you create?
Coding convention?
Extra tests?
Changelog?
Target branch?
One last thing