Closed
Description
This is being developed on the Update: the next
branchnext
branch has been merged into `master.
We should release 0.2.0 or perhaps 1.0.0
and make cargo-fuzz
start using it!
Prerequisites:
Perhaps name the crate(Split out into Split crate intolibfuzzer
since it's more high level than than just sys stuff?libfuzzer
andlibfuzzer-sys
#55)Change API to be more like honggfuzz-rs Change API to be the same as Honggfuzz-rs and eventually AFL.rs #51Update to Arbitrary 0.3.0 Tracking issue for 0.3.0 release arbitrary#19Provide a way to run Debug on the output Provide way to run Debug on fuzzer output #47 (maybe Include Debug-formatted output in fuzzer output #48)
Metadata
Metadata
Assignees
Labels
No labels
Activity
fitzgen commentedon Dec 30, 2019
+1 on teasing apart the bit that builds and links libfuzzer from the integration with
arbitrary
and the macro that users actually use and all that.fitzgen commentedon Jan 10, 2020
@Manishearth since we don't want to mess with master because of all the existing git dependencies, what if we do this:
rust-fuzz/libfuzzer-rs
repo that is a fork (but not in the github sense) of this repoThoughts?
Manishearth commentedon Jan 11, 2020
Manishearth commentedon Jan 11, 2020
fitzgen commentedon Jan 13, 2020
I don't have admin access, so I can't do this shuffling. Happy to do it if you or someone else gives me that access! :)
Manishearth commentedon Jan 14, 2020
Made you an org admin, go nuts!
fitzgen commentedon Jan 14, 2020
Huh... I still don't have access to the admin panel or anything. Can't find an email from github that I need to accept or anything like that either...
Manishearth commentedon Jan 14, 2020
I'd upgraded you to org admin, but maybe that didn't go through. Try now?
fitzgen commentedon Jan 14, 2020
Ok, now I have it! Thanks!
fitzgen commentedon Jan 14, 2020
Ok, this repo is now
rust-fuzz/libfuzzer
!We also have an archived
rust-fuzz/libfuzzer-sys
repo so that the old git deps will continue to work and we don't break anyone's existing installs.fitzgen commentedon Jan 14, 2020
I also merged the
next
branch intomaster
on this new repo, btw.fitzgen commentedon Jan 14, 2020
Ok I made an initial attempt at splitting this crate apart into
libfuzzer
andlibfuzzer-sys
. The libfuzzer build, and its interaction with sanitizers and code coverage, is so fragile that I immediately ran into linker errors despite only doing code motion between crates. I don't have the energy for that today.https://github.com/fitzgen/libfuzzer/tree/split-libfuzzer-and-libfuzzer-sys if anyone else wants to take a look at it.
But I think I'm going to skip it for the 0.2.0 release of
libfuzzer-sys
.Bump to version 0.2.0 and update README/Cargo.toml metadata
4 remaining items