infra: Add missing flags for coverage feedback #12789
Open
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.
There are some projects rely on the CFLAGS provided by OSS-Fuzz to do the coverage instrumentation.
For example:
https://github.com/h2o/picotls/blob/d13ff3b9fcbc084572a56a65a6d188643a0bf2fb/CMakeLists.txt#L251-L268
Although the
-fsanitize=fuzzer-no-link
is provided inoss-fuzz/infra/base-images/base-builder/Dockerfile
Lines 97 to 102 in 92d61f8
But due to the coverage flag overrides,
-fsanitize=fuzzer-no-link
is omitted.oss-fuzz/infra/base-images/base-builder/compile
Lines 97 to 102 in 92d61f8
This results in no feedback when running fuzzer, it implies that these fuzzers are all running with a black box fuzzing setting?
The CFLAGS when compiling shown in the log
Steps: