videolan/ffmpeg
1
Fork 0
mirror of https://git.videolan.org/git/ffmpeg.git synced 2024-07-29 07:18:22 +02:00
Code Releases Activity

doc: Mention memory allocation in the fuzz testing section

Browse Source 
It's obviously undesireable to blindly allocate memory based on
a damaged 'size' value, for example.

Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
This commit is contained in:
Derek Buitenhuis 2013-01-06 13:25:07 -05:00
parent dc3e12d1cb
commit ac2603be28
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/developer.texi
View File

@ -453,7 +453,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 Did you test your decoder or demuxer against damaged data? If no, see
tools/trasher, the noise bitstream filter, and tools/trasher, the noise bitstream filter, and
@uref{http://caca.zoy.org/wiki/zzuf, zzuf}. Your decoder or demuxer @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 @item
Does the patch not mix functional and cosmetic changes? Does the patch not mix functional and cosmetic changes?
@item @item