Closed kokanin closed 5 years ago
There is an interestingness test in the funfuzz repository called crashesat that allows you to mark a specific type of symptom as "interesting".
Perhaps you'd like to give that a try?
this looks like it can be worked into something, thanks!
I have an application with two crash paths, where one is interesting (for me) and the other not. When reducing the test case, I end up with a small file triggering the uninteresting part - any bright ideas on how to mark a specific crash type (stack overrun, div by 0 or similar) as not interesting without implementing a full debugger?