Now crashes with a stacktrace and uses 'overwrites-const-input' as the error
message instead of 'out-of-memory'.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
compiler-rt/lib/fuzzer/FuzzerLoop.cpp | ||
---|---|---|
518 ↗ | (On Diff #221874) | I don't see a benefit to printing this stack trace -- it will always be in libFuzzer code. |
521 ↗ | (On Diff #221874) | Also not sure if stats are actually valuable. Overwriting the input means there's a bug in the fuzz target, probably not the library being fuzzed. |
Comment Actions
I think Matt is right, but I wouldn't mind to have the stacktrace and stats just to be consistent with the other crashes. Also, having a stacktrace should increase the chances that such a crash would be handled by fuzzing infrastructure and reported to people.