| commit | a115942ed69762206f87c680ef7ec98de3382fa6 | [log] [tgz] |
|---|---|---|
| author | mtklein <mtklein@chromium.org> | Fri Jan 15 05:46:54 2016 -0800 |
| committer | Commit bot <commit-bot@chromium.org> | Fri Jan 15 05:46:54 2016 -0800 |
| tree | 9afd175bac06573aac0bc77f602c6f3779d2ba9b | |
| parent | 0a35620a16b368356888d15771392fb00cbb777d [diff] |
fuzz: signalBug() / signalBoring() Instead of a single ASSERT macro, this switches to two new methods: - signalBug(): tell afl-fuzz there's a bug caused by its inputs (by crashing) - signalBoring(): tell afl-fuzz these inputs are not worth testing (by exiting gracefully) I'm not seeing any effect on fuzz/s when I just always log verbosely. signalBug() now triggers SIGSEGV rather than SIGABRT. This should make it work with catchsegv more easily. BUG=skia: GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1585353002 Review URL: https://codereview.chromium.org/1585353002