diff options
| author | Michael Niedermayer <michaelni@gmx.at> | 2013-01-08 12:46:53 +0100 |
|---|---|---|
| committer | Michael Niedermayer <michaelni@gmx.at> | 2013-01-08 12:46:59 +0100 |
| commit | 32cf37d097db526c1e42810f04463b78bb6306f2 (patch) | |
| tree | cdff03fa31461f5f36ab4b190a60221131bf23c8 /doc/developer.texi | |
| parent | adc7296aa5b2f1027f55e14b556129b72080f389 (diff) | |
| parent | dc3e12d1cb65d74fb120197ce869a205718b6715 (diff) | |
Merge commit 'dc3e12d1cb65d74fb120197ce869a205718b6715'
* commit 'dc3e12d1cb65d74fb120197ce869a205718b6715':
doc: Mention zzuf in the fuzz testing section
Merged-by: Michael Niedermayer <michaelni@gmx.at>
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 7fa8179cc0..14055305c8 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -453,7 +453,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? |