Skip to content
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

Create fuzzer-specific coverage build #2044

Open
renatahodovan opened this issue Sep 9, 2024 · 0 comments
Open

Create fuzzer-specific coverage build #2044

renatahodovan opened this issue Sep 9, 2024 · 0 comments

Comments

@renatahodovan
Copy link

I am trying to integrate a libFuzzer-based structure-aware fuzzer that works with a corpus in an internal representation form. This means that the first step of the SUT or benchmark is always decoding the received test from the internal representation, similar to protobuf-based structure-aware solutions. For this, the benchmark build needs to know which fuzzer it is building the binary for. This works, except for the coverage build, where I couldn't find a way to inform the build that a decode step is required, as it automatically prepares the libFuzzer configuration. So the question is, is there any way to communicate the name of the corpus-generating fuzzer to the build script during the coverage build?

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

No branches or pull requests

1 participant