Module: libav Branch: master Commit: ac2603be28602bea76cf38bdbf37aead0dc2979a
Author: Derek Buitenhuis <[email protected]> Committer: Derek Buitenhuis <[email protected]> Date: Sun Jan 6 13:25:07 2013 -0500 doc: Mention memory allocation in the fuzz testing section It's obviously undesireable to blindly allocate memory based on a damaged 'size' value, for example. Signed-off-by: Derek Buitenhuis <[email protected]> --- doc/developer.texi | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/doc/developer.texi b/doc/developer.texi index c10d44a..691a907 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. 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 _______________________________________________ libav-commits mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-commits
