Re: [Devel] Crashing bug

[Werner LEMBERG]

> a font that was embedded in a pdf file causes ftstring to crash. The
> font can be downloaded from
> http://bepdf.sourceforge.net/temp/font.zip

Thanks for the report.  Note that the font is invalid; t1disasm gives
the following:

  /seven {
    74 -32 12 13 -11 -74 rrcurveto
    79 11 rlineto
    5 -21 -73 -244 25 0 rrcurveto
    5 0 -9 -8 -5 0 rrcurveto
    0 0 -13 6 -6 0 rrcurveto
    -39 0 7 -30 61 0 rrcurveto
    28 0 -22 7 0 rrcurveto
    2 -53 rlineto
    -4 0 -22 -19 -61 0 rrcurveto
    9 0 54 4 257 0 rrcurveto
    86 0 -192 9 54 0 rrcurveto
    2 0 -24 7 -30 0 rrcurveto 
    0 0 256 div
    hsbw
    284 34 62 20 -63 12 rrcurveto
    25 257 rlineto
    ...

A glyph must start like this:

  /six {
    0 0 256 div     
    hsbw
    -14 30 hstem
    336 38 hstem
    40 89 vstem
    381 85 vstem 
    40 236 rmoveto
    ...

As you can see, the `hsbw' command isn't at the start of glyph `seven'
(and the following ones), and there isn't a `Xmoveto' command to add a
first point to the current path.

I've fixed this in the CVS now -- I ask all of you to test the Type 1
module, checking whether I've introduced bugs.


    Werner