Hi,

> > - Memory leak! We're loosing memory, apparently when moving from one scene
> > to another. Lots of it, too (maybe it's just pic_buffer_size != 0 being
> > interpreted as "infinite", but I don't think so).
> > 
> > Reliably finding the memory leak(s) will require slighly modified versions
> > of malloc() and friends, unless somebody already has a good tool for that.
> 
> Quaoting from the malloc man page:

[...]

Ah, thanks! However, this is mostly for finding dereferenciations of
invalid pointers etc; the situation we appear to be having is that a
pointer to a valid allocated memory block is being overwritten without the
memory block being freed.

> Also, check out electric fence (written by bruce perens).  It comes standard
> on most linux distros.

We have the --with-efence option to enable it at 'configure' time, but it
aborts in libggi's manual X sync thread on my box. Again, this doesn't
find memory leaks.

> Is that the sort of stuff that you were looking for, or did I misunderstand?

It is helpful and will probably find some other bugs for us, but I don't
think it's applicable to this specific problem. Thanks anyway!

llap,
 Christoph


Reply via email to