Matthew Lye wrote: > If I understand correctly, the leak reporting relies on whether or not > there's a pointer to the memory block, or some such thing. It also > relies on the use (ultimately) of the system's standard malloc, I > think. The documentation is a bit above my comprehension level for > regular casual reading, which is all I've done so far.
You should compile gtk-gnutella with --cflags=-DMALLOC when looking for memory leaks. -- 1000 octets = 1 ko = 1 kilooctet; 1024 octets = 1 Kio = 1 kibioctet 1000^2 octets = 1 Mo = 1 megaoctet; 1024^2 octets = 1 Mio = 1 mebioctet 1000^3 octets = 1 Go = 1 gigaoctet; 1024^3 octets = 1 Gio = 1 gibioctet ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ gtk-gnutella-devel mailing list gtk-gnutella-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
