Re: [Devel] Debugging Memory Manager added to FreeType sources

[David Turner]

Hi Tom,

 I made a small CVS commit, could you try to see if this fixes
 your problem. Otherwise, an obvious solution is to use a debugger
 to see if ft_mem_debug_alloc is called (or to see how many times
 "parse_subrs" and al. are called for your font)..

Regards,

- David



Tom Kacvinsky a écrit :
> 
> On my *local* copy, I reintroduced the bugs so I could see how this debug 
> memory
> stuff works.  So far, I haven't been able to get it to print any kind of
> messages about leaks. :(
> 
> On Mon, 22 Oct 2001, David Turner wrote:
> 
> > Hi Tom,
> >
> > Tom Kacvinsky a écrit :
> > >
> > > I just clobbered the FT2 directory, did a fresh CVS checkout, recompiled 
> > > the code,
> > > set the envrionment variable, and still, ftlint does not report memory 
> > > leaks at
> > > the end of its run...
> > >
> > > I must be doing something stupid...
> > >
> >
> > Do you mean that you didn't re-introduced the t1load.c bugs back..
> > seeing no memory leaks shouldn't be surprising then  ??
> >
> > Regards,
> >
> > - David
> >
> > _______________________________________________
> > Devel mailing list
> > address@hidden
> > http://www.freetype.org/mailman/listinfo/devel
> >
> 
> _______________________________________________
> Devel mailing list
> address@hidden
> http://www.freetype.org/mailman/listinfo/devel