Bill Pringlemeir wrote: >> I have a segment violation inside malloc. Here is the trace, it is >> not very useful to me, but maybe someone else can divine something >> from it. The frame 3 is very weird. Is the stack trace also bad?
On 8 Feb 2005, [EMAIL PROTECTED] wrote: > Well, that's most likely a heap corruption indeed. The stacktrace > might be useless due to switching to an alternate stack at some > stage. On the other hand, the core might just be corrupted. There's > no way to find the cause with this little information. Purify would > be a help. I have updated the source and recompiled with dmalloc. This didn't catch the problem. I have several core files and they often mention possible stack corruption. I don't know where to get 'Purify'. I only see a 'Rational Purify' from IBM and it looks like a commercial product. Did you have a URL/pointer on which memory product to use. Would electric fence work? Looks like it also concentrates on malloc/free. Could this be an actual stack overflow? The traces always look different. fwiw, Bill Pringlemeir. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
