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.

Sign up for GitHub

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

Jump to bottom

consider committing corpus directories #7

Open
frewsxcv opened this issue Mar 2, 2017 · 5 comments
Open

consider committing corpus directories #7

frewsxcv opened this issue Mar 2, 2017 · 5 comments

Comments

@frewsxcv
Copy link
Member

frewsxcv commented Mar 2, 2017

good idea? bad idea?
@Manishearth
Copy link
Member

I think it's a good idea.

@Manishearth
Copy link
Member

You may sometimes want to run with an empty corpus to un-train the fuzzer and try a different approach.

@killercup killercup mentioned this issue Mar 14, 2017
Merged
@frewsxcv
Copy link
Member Author

This is blocked on #66

@killercup
Copy link
Member

We can revisit this now if you want to

@frewsxcv
Copy link
Member Author

frewsxcv commented May 1, 2018

My main hesitation here is that it could blow up the side of the git object database as some corpus files can get pretty large. This could be FUD though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@killercup @frewsxcv @Manishearth