[libav-commits] doc: Mention zzuf in the fuzz testing section

Derek Buitenhuis git at libav.org
Mon Jan 7 20:57:26 CET 2013

Module: libav
Branch: master
Commit: dc3e12d1cb65d74fb120197ce869a205718b6715

Author:    Derek Buitenhuis <derek.buitenhuis at gmail.com>
Committer: Derek Buitenhuis <derek.buitenhuis at gmail.com>
Date:      Sun Jan  6 13:24:06 2013 -0500

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>


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

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?
     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.
     Does the patch not mix functional and cosmetic changes?

More information about the libav-commits mailing list