diff options
| author | Derek Buitenhuis <derek.buitenhuis@gmail.com> | 2013-01-06 13:24:06 -0500 |
|---|---|---|
| committer | Derek Buitenhuis <derek.buitenhuis@gmail.com> | 2013-01-07 14:55:49 -0500 |
| commit | dc3e12d1cb65d74fb120197ce869a205718b6715 (patch) | |
| tree | 9b5c39aca28f9cb2c9f24f29de1d4c6ea3b04190 /doc/developer.texi | |
| parent | b5f9b9ac3681acb06d95530f34660ba9fe225305 (diff) | |
doc: Mention zzuf in the fuzz testing section
It's pretty much the best tool for the job, and it's what we
all use now anyway.
Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
Diffstat (limited to 'doc/developer.texi')
| -rw-r--r-- | doc/developer.texi | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/developer.texi b/doc/developer.texi index f374614463..c10d44a2c0 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -451,7 +451,8 @@ send a reminder by email. Your patch should eventually be dealt with. other security issues? @item Did you test your decoder or demuxer against damaged data? If no, see - tools/trasher and the noise bitstream filter. Your decoder or demuxer + tools/trasher, the noise bitstream filter, and + @uref{http://caca.zoy.org/wiki/zzuf, zzuf}. Your decoder or demuxer should not crash or end in a (near) infinite loop when fed damaged data. @item Does the patch not mix functional and cosmetic changes? |