___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
(This is resend as I did an earlier direct response)
Think I found it.
I tried 'relaxing' the release build optimizations all the way back to the
debug settings.
No difference
So I analyzed how the memory was allocated. I realized that EVERYTHING was
alloced from ft_alloc(memory, size) so I
Have been reading DrMemory. However, this isnt' unusual for MS release builds
in particular.
As I mentioned and you're obviously aware, why DON'T you used calloc internally?
This is running rock solid with that 1 change in ft_alloc()
I consider this fixed until/unless something else goes boom
And, in case I didn't mention, THANK YOU so much for this wonderful library and
your prompt responses.
-Original Message-
From: werner.lemb...@gmx.de [mailto:werner.lemb...@gmx.de] On Behalf Of Werner
LEMBERG
Sent: Saturday, March 22, 2014 1:07 PM
To: ch...@burfoots.com
Subject: Re:
Downloaded from git site - ft253.zip
Extracted
Ran CMake 2.8
Config
Gen
Opened ran .sln in VStudio 2010
Built debug static
Built release static
Builds static lib
Debug sample runs fine
Release sample exception in FT_New_Face
Top of ft_fseek()
Looks like a corrupt stack ?
