I tested fuzzy matching through dmalloc and saw the reason for the mem corruption.
That said, I will switch dmesh fuzzy matching to FALSE by default on the next version, because it is an O(m*n) alogorithm, and fuzzy matching is really INNEFFICIENT (allocates memory to perform its operation, and it's not an optimal algorithm either). Also, the algorithm dumps perfectly valid locations. The only remaining leaks seem to be in the atoms. Those I cannot find with dmalloc and will need to run valgrind to find them. - (2003.02.05 - RAM) * Fixed dmesh fuzzy matching memory corruption. * Send PUSH messages at max TTL value, not my TTL in case it needs re-routing. * Added missing memory cleanup to shutdown calls, preventing leak detection. Raphael ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
