diff options
| author | Michael Niedermayer <michaelni@gmx.at> | 2013-01-08 12:48:21 +0100 |
|---|---|---|
| committer | Michael Niedermayer <michaelni@gmx.at> | 2013-01-08 12:49:02 +0100 |
| commit | 3a0bac27b3c851924a5fbde5301a3ad6bf951aba (patch) | |
| tree | 10a51504191ec537d0858f3c941b70875d08577b /doc/developer.texi | |
| parent | 32cf37d097db526c1e42810f04463b78bb6306f2 (diff) | |
| parent | ac2603be28602bea76cf38bdbf37aead0dc2979a (diff) | |
| download | ffmpeg-3a0bac27b3c851924a5fbde5301a3ad6bf951aba.tar.gz | |
Merge commit 'ac2603be28602bea76cf38bdbf37aead0dc2979a'
* commit 'ac2603be28602bea76cf38bdbf37aead0dc2979a':
doc: Mention memory allocation 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 14055305c8..fce842a006 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -455,7 +455,8 @@ send a reminder by email. Your patch should eventually be dealt with. Did you test your decoder or demuxer against damaged data? If no, see 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. + should not crash, end in a (near) infinite loop, or allocate ridiculous + amounts of memory when fed damaged data. @item Does the patch not mix functional and cosmetic changes? @item |