[ft-devel] bug: valgrind uninit mem usage - linux freetype v2.7

[- -]

valgrind reports this problem originating in libfreetype (v2.7)
==10001== Conditional jump or move depends on uninitialised value(s)

I have a fix. Tested and working. Just a small change on one line.

File: /src/freetype-2.7/src/smooth/ftgrays.c
Function: gray_raster_render(..)
[line 1867]    gray_TWorker  worker[1];
=>
[line 1867]    gray_TWorker  worker[1]={0};

The same bug is also in the v2.7.1 sources (line 1848).
This problem may be indicative of a deeper problem as to why 'worker' is not 
initialized later, but at least this
fix gives us a solid base rather than /random values/, and keeps valgrind clean.

Thank you for the wonderful freetype library.