It's pretty much the best tool for the job, and it's what we
all use now anyway.

Signed-off-by: Derek Buitenhuis <[email protected]>
---
 doc/developer.texi |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/developer.texi b/doc/developer.texi
index 4113cbf..95c4432 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?
-- 
1.7.10.4

_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to