Add weak libfuzzer hook fallbacks and macOS-only CI job to test it #3681
+180
−0
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.
Regarding #3649, on macOS, linking libafl_libfuzzer fails when optional libfuzzer hook symbols are not provided, since the linker does not tolerate unresolved references even when the hooks are intended to be optional.
To fix this, I added weak fallback implementations for the custom mutator and crossover hooks into FuzzerInterceptors.cpp. They ensure that the symbols always exist at link time, and still allow for user-defined hooks to override them if they are present.
I also added a macOS-only CI job to build libafl_targets and libafl_libfuzzer to check if it works.
Let me know if there's anything else I should change!