Skip to content

Tracking issue for 0.2.0 release #52

Closed
@Manishearth

Description

@Manishearth
Member

This is being developed on the next branch Update: the next 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:

Activity

fitzgen

fitzgen commented on Dec 30, 2019

@fitzgen
Member

Perhaps name the crate libfuzzer since it's more high level than than just sys stuff?

+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

fitzgen commented on Jan 10, 2020

@fitzgen
Member

Perhaps name the crate libfuzzer since it's more high level than than just sys stuff?

@Manishearth since we don't want to mess with master because of all the existing git dependencies, what if we do this:

  • Create a new rust-fuzz/libfuzzer-rs repo that is a fork (but not in the github sense) of this repo
  • Archive this repo with a README noice to use that new repo instead
    • And now all the existing git deps will continue to work forever
  • And then we actually continue dev on the new repo:
    • transfer relevant issues over
    • split sys and highlevel utils crates (but still in same repo/workspace)
    • etc

Thoughts?

Manishearth

Manishearth commented on Jan 11, 2020

@Manishearth
MemberAuthor
Manishearth

Manishearth commented on Jan 11, 2020

@Manishearth
MemberAuthor
fitzgen

fitzgen commented on Jan 13, 2020

@fitzgen
Member

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

Manishearth commented on Jan 14, 2020

@Manishearth
MemberAuthor

Made you an org admin, go nuts!

fitzgen

fitzgen commented on Jan 14, 2020

@fitzgen
Member

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

Manishearth commented on Jan 14, 2020

@Manishearth
MemberAuthor

I'd upgraded you to org admin, but maybe that didn't go through. Try now?

fitzgen

fitzgen commented on Jan 14, 2020

@fitzgen
Member

Ok, now I have it! Thanks!

fitzgen

fitzgen commented on Jan 14, 2020

@fitzgen
Member

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

fitzgen commented on Jan 14, 2020

@fitzgen
Member

I also merged the next branch into master on this new repo, btw.

fitzgen

fitzgen commented on Jan 14, 2020

@fitzgen
Member

Ok I made an initial attempt at splitting this crate apart into libfuzzer and libfuzzer-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.

added a commit that references this issue on Jan 14, 2020
3d9eb35

4 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @fitzgen@Manishearth

      Issue actions

        Tracking issue for 0.2.0 release · Issue #52 · rust-fuzz/libfuzzer