And I think there should be more change in this code section:
'limit' should be reset by 'buffer + readsize' in where readsize is
actual read size.
Please provide a patch.
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
On Tue, 08 Nov 2005 10:12:19 +0100 (CET)
Werner LEMBERG [EMAIL PROTECTED] wrote:
And I think there should be more change in this code section:
'limit' should be reset by 'buffer + readsize' in where readsize is
actual read size.
Please provide a patch.
Excuse me, give me 4 hours.
Regards,
On Tue, 8 Nov 2005 19:17:02 +0900
[EMAIL PROTECTED] wrote:
On Tue, 08 Nov 2005 10:12:19 +0100 (CET)
Werner LEMBERG [EMAIL PROTECTED] wrote:
And I think there should be more change in this code section:
'limit' should be reset by 'buffer + readsize' in where readsize is
actual read size.
Hi,
Thanks for the note. Sorry but I do not have the test case, I just
looked at the code and found out the bug.
And I think there should be more change in this code section: 'limit'
should be reset by 'buffer + readsize' in where readsize is actual
read size.
Thanks,
TK
2005/11/3, [EMAIL
When this function locates 'StartData' , it reads in by '256 + 10 -
buff_len' from stream. Sometimes, the font data after 'StartData' is
not very long and stream read function fails in this case.
I think stream-size should be considered to get the correct reading length.
