Re: [Freetype] gsf segv in freetype2?

[Werner LEMBERG]

> As I'm a beta tester for SuSE I told them the problem and they
> replied that libfreetype has some problems regarding gsf-Files
> causing all apps to crash with SEGV.

Indeed, there might be problems.  Since there is no exact format of a
GSF, FreeType sometimes thinks such fonts are Type 1 fonts
(e.g. u004006t.gsf looks similar enough to a real Type1 font that it
isn't rejected by FreeType's ftview demo program -- of course, trying
to render glyphs always gives errors).

I couldn't manage to get a SEGV with the FT2 demo programs, though...

> Now I've looked around a bit and found a patch included in the
> PLD-RPMs of libfreetype2.  I've attached it to this mail.  It's for
> 2.0.4 but they seem to apply it to all versions up to and including
> 2.0.6.

Thanks.  In case you can find out who wrote that patch I can give
credit to him or her.

> I wanted to ask if this problem and the patch is already known - and
> if this bug will be corrected in future versions of libfreetype.

I've just applied a slightly modified version of the patch to the CVS.

> Or is it just a dirty hack and the problem lies elsewhere (not at
> libfreetype?).

No idea, but the problem was real -- please report whether the fix
really removes the SEGVs you've experienced.

> As far as I've understood, libfreetype has nothing to do with
> gsf-files - but it crashes when trying to read them.  Would it be
> possible to make libfreetype recognize that it reads a gsf-file and
> stop trying to interprete it?

I think this is impossible due to the reasons explained above.


    Werner