Skip to content

Fix a number of instrumentation issues that occur when other projects use the fuzzing rules. - #91

Merged
stefanbucur merged 4 commits into
masterfrom
envoy-integration
Dec 8, 2020
Merged

stefanbucur merged 4 commits into
masterfrom
envoy-integration

Conversation

@stefanbucur

Copy link
Copy Markdown
Collaborator
  • The build flags need to be referenced with the absolute workspace name, so the names resolve correctly when imported in a different repo.
  • The fuzzing build mode is now optional so it can be disabled in the projects that wish so.

…e top-level fuzz test is instrumented.

Without this change, any other binary that may be built on the transitive dependency chain will also get linked with libFuzzer, resulting in a linker error (duplicate main functions).
* The build flags need to be referenced with the absolute workspace name, so the names resolve correctly when imported in a different repo.
* The fuzzing build mode is now optional so it can be disabled in the projects that wish so.
Base automatically changed from libfuzzer-linkopts to master December 8, 2020 02:15
@stefanbucur
stefanbucur merged commit c72ed72 into master Dec 8, 2020
@stefanbucur
stefanbucur deleted the envoy-integration branch December 8, 2020 02:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants