[FFmpeg-cvslog] doc: Mention zzuf in the fuzz testing section

Derek Buitenhuis git at videolan.org
Tue Jan 8 12:47:51 CET 2013


ffmpeg | branch: master | Derek Buitenhuis <derek.buitenhuis at gmail.com> | Sun Jan  6 13:24:06 2013 -0500| [dc3e12d1cb65d74fb120197ce869a205718b6715] | committer: Derek Buitenhuis

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 at gmail.com>

> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=dc3e12d1cb65d74fb120197ce869a205718b6715
---

 doc/developer.texi |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/developer.texi b/doc/developer.texi
index f374614..c10d44a 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?



More information about the ffmpeg-cvslog mailing list