> OK, I came up with 2 regex expressions to try and find inline code
> sequences, and was able to replace 394 `...' quotes to `...`. All
> other quotes will be converted to '...' (these changes were done in
> markify.py).
>
> However, this is *not* fool-proof, and many variable names would
>
Hi everyone,
this is a quick update about my GSoC project :)
Recently, I explored ways of splitting the fuzz targets that keep
engineering and runtime overhead at a minimum (esp. the upcoming engineering
efforts) while providing flexibility when it comes to designing fuzz targets
that target
>
> >There is not a single font driver in FreeType that uses `FT_FILE'.
> >It's definitely the wrong interface. FreeType either accepts font
> >files or fonts that are preloaded into a memory buffer. For the
> >latter you can't use `fopen' and friends; this is another reason for
> >being the
> When the gf driver enters the gf_load_font in gflib.c, if we use
> stream->descriptor.pointer to get the file pointer and comment out
> the fopen I get a segmentation fault. And if the fopen is used it
> works fine.
>
> Like here:
>
> FT_FILE* fp = (FT_FILE*)stream->descriptor.pointer;
