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

Have CrashMonkey behave more like a fuzzer #122

Open

vijay03 opened this issue Nov 9, 2018 · 1 comment

Assignees

Labels

Member

vijay03 commented Nov 9, 2018

Have CrashMonkey run in a "fuzzer" mode where:

It takes as input running time T. It should terminate after this specified time.
It randomly picks a target workload in the configured state space (right now it explores everything)
It stores a persistent state with the workloads it has already explored so that it doesn't explore them in the next invocation (a bloom filter with test IDs would probably work)

vijay03 added the help wanted label

Member Author

vijay03 commented Dec 13, 2018

Check out AFL: http://lcamtuf.coredump.cx/afl/

MatthewHinton56 self-assigned this

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