Yeah. BTW, does your code work with *any* previous FreeType
version? Then bisecting might still be useful.
Yes, I use Freetype more than 10 years and it always worked. But
this is the first time I have tried win64.
This means that the error is specific to win64.
Bisecting looks like a lot of work and I am not very good at working
with CVS, but I will try to find time.
Well, we no longer use CVS but git, and it's really quite easy: You
check out a certain state of the repository, you run the compilation,
you call your program, and you check whether it crashes. This makes
either a `good' or a `bad' state, and git then provides you with
another version to repeat until you get the problematic commit. Have
a look at the tutorial link I've sent in a previous e-mail.
HOWEVER, since both the old and the new version fails with win64, it
doesn't make sense to bisect – except you find an old FreeType version
that works.
As I wrote, debugger itself is a little buggy an Borlands's win64
compiler,
Uh, oh, this slipped my radar :-) Buggy compilation, buggy debugger...
but I am trying this way as well and I will tell you if I get useful
information.
Thanks!
Werner