Avoid the "replace main" trick

Open
#46 5 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, rust
Domain
testing-qa

Research direction

Start with libFuzzer's existing main() and FuzzerDriver entry points, then review how this repository links its Rust fuzz target without main(). The work is complete when a compile-time option can disable libFuzzer's main and a user-defined main can call libfuzzer::fuzz(...).

Written by the indexing model from the issue text.

Description

breaking change

The way libfuzzer works is that libfuzzer itself contains a main(), and you link in a binary that contains a hook but not main().

This is kind of awkward, ideally we can get rid of this requirement and instead have a system where you define main() and call libfuzzer::fuzz(|x: &[u8]| {...}) when ready.

Of course, this won't work without changes to libFuzzer itself. Ideally we can add a compile time flag that disables main() and routes everything through FuzzerDriver.

Dominant language
C++
Stars
267
Forks
51
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-fuzz/libfuzzer

All issues in rust-fuzz/libfuzzer

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.