[EMAIL PROTECTED] wrote: > This is good evidence that there may be a problem, but doesn't help anybody > to find it. If you can construct a few session transcripts that reliably > cause memory leaks, we can start tracking it down.
I'm thinking of fixing the code so it will work with libgc. I remember that was a very instructive exercise that helped the 2.0 code significantly. I'm not sure though glib and gmime are gc-safe. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
