We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
When running with --engine afl, the only output shown is the AFL dashboard.
--engine afl
The crashes are saved to a .../crashes/ directory. I assume the files contain the input.
.../crashes/
What is the suggested workflow for actually getting debugging output for the crashes, like stdout/err and a backtrace?
I guess I'd have to manually re-run the test with the appropriate input, but how exactly is that supposed to work with #[test] cases?
#[test]
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When running with
--engine afl, the only output shown is the AFL dashboard.The crashes are saved to a
.../crashes/directory. I assume the files contain the input.What is the suggested workflow for actually getting debugging output for the crashes, like stdout/err and a backtrace?
I guess I'd have to manually re-run the test with the appropriate input, but how exactly is that supposed to work with
#[test]cases?The text was updated successfully, but these errors were encountered: