>> The current function used for the fuzzer doesn't cover GX stuff at
>> all. We have to extend it step by step to get a better FreeType
>> coverage.
>
> Let's start from here.
> I think the more sustainable approach is to commit the target
> function into the FreeType git first.
> I'll then re-target the bot to use that file instead of my own.
> Once that works, one of the domain experts (i.e. not me :) will be
> able to add more stuff there.
> This way you will fully control what functionality is actually being
> fuzzed, and I will just monitor the infrastructure.
> Does that sounds reasonable?
Yep. If you like, I can give you write access so that you can quickly
adjust the fuzzer function if necessary. And please resend the
function you are currently using for testing.
Werner
_______________________________________________
Freetype-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype-devel
