#11400: Consider adding a fuzzer for filtergraphs
-------------------------------------+-------------------------------------
Reporter: somehacker | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Component: avfilter
Version: git-master | Resolution:
Keywords: fuzzer | Blocked By:
fuzzing test filters |
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by somehacker):
Forgot to mention that since the syntax of the filter graphs are highly
structured, maybe it would be worth it to create a custom mutator which
would always produce syntactically valid filtergraph expressions such that
the majority of them don't get rejected at the parsing stage. I think this
can be done by programmatically going through the source code and then
processing the different filters and their options and adding a handler
for each type of option (AV_OPT_TYPE_INT, AV_OPT_TYPE_STRING,
AV_OPT_TYPE_FLOAT etc etc). Then adding mutation strategies, like adding
options, removing options, mutating option value, adding input pads,
removing input pads or output pads and so on. This is basically on the
level of "metaprogramming" and quite ambitious but I think it is doable.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11400#comment:1>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".
