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

diff --git a/doc/developer.texi b/doc/developer.texi
index f3746144639198f605584990b3b86f2c1fa46372..c10d44a2c05132e66973387ef684587249b6a9cb 100644 (file)
--- 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?