-
Notifications
You must be signed in to change notification settings - Fork 16
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.
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
Missing documentation how to reproduce faults #18
Comments
|
Yes, I read that part but it's not 100% clear how can i run the crashses or the testcases with my program. |
To be clearer. I implemented the example in a C program called If i run |
Hi @francescoschembri. AFAIK, Eclipser is tool that could give you a crash, but it cannot show you the program path or minimize the input to know we exactly which bytes are important. If you want to understand how and why you program crashed, you should use a debugger such as gdb. You can take a look to a tutorial for debugging a crash here. |
|
Ok so it's a decision to focus just on the fuzzing and not also on the other stuffs. Thanks for the clarification. |
Please add the documentation (and the feature if it's missing) of how to reproduce crashes and parse the bytes to tell user which are the inputs that made the program crash.
The text was updated successfully, but these errors were encountered: