Workflow for Debugging/Reproducing Crashes (AFL)
theduke opened this issue · 0 comments
theduke commented
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?