On 29 Mar 2005, [EMAIL PROTECTED] wrote: > Bill Pringlemeir wrote: >>> Thus, Purify would come in quite handy as I don't really have an >>> idea where to start looking at all. > >> I guess I should look at getting that and installing it. I have >> dmalloc installed, as well as the stack smasher and gprof. > > The best free alternative for purify seems to be > valgrind. Unfortunately, it works only on Linux/x86 at the > moment. If someone could check Gtk-Gnutella regularly it would > certainly help.
I have been banished to Mainz. When I get home, I will try valigrind. I have also been trying to get the source to run through splint... Anyways, Gtkg was running for several days until my computer reset yesterday at about 1300GMT. I believe this instance was running for over a week. Instead of running the Mandrake 10 KDE, I ran under TWM. It does appear that my problem could be related to resource depletion. That would be the only way to explain the extra longevity. Under KDE and TWM, I was running as a leaf node. I was also compiling with "Gprof" instrumentation. This seems to cause many calls to "time(0)" under some circumstances. I noted the dialogs not repainting, in a previous post. This was due to this effect; I don't know if this is many un-necessary function calls in Gtkg or if it is a gprof problem... I did confirm that a lot of Gtkg's time is spent in the SHA routine. I still have many corrupted stack traces that usually end with "mallopt()". I do believe that there was some memory problem previously. I have not compiled/updated since Mar 19th. Sorry, I can not be of more help. Bill Pringlemeir. ------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/Info/Sentarus/hamr30 _______________________________________________ Gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
