[9275] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: misc gtk mis-understandings
daemon@ATHENA.MIT.EDU (Johannes Keukelaar)
Wed Oct 14 05:18:48 1998
To: gtk-list@redhat.com
From: johannes@nada.kth.se (Johannes Keukelaar)
In-reply-to: Your message of "Tue, 13 Oct 1998 18:07:29 BST."
<000101bdf6cb$f58a08a0$904e95c1@default>
Date: Wed, 14 Oct 1998 11:18:26 +0200
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
//
//> That sounds like pointer corruption to me. Strange things can
//> happen when you
//> have corrupted pointers or memory. Have you tried running with
//> electricfence or
//> ccmalloc? They work for me when I have problems like that.
//
//Can you describe how you compile/run a program to work with these.
//I think it should be part of the GTK docs.
For ccmalloc, it's a question of downloading, compiling, linking (with
-lccmalloc -ldl) and running. You can then fine-tune what gets detected by
editing a config file and rerunning your program. It detects things like
underwrite and overwrite of allocated memory, freeing memory twice, writing to
memory after it's been freed, etc.
It knows how to produce a log file of all memory leaks complete with backtrace
(although that may not be of much use under gtk+, since gtk+ is full of
(intentional?) memory leaks).
//Damon
Johannes.
--
"In film you will find four basic story lines. Man versus man, man versus
nature, nature versus nature, and dog versus vampire." - Steven Spielberg
Self-professed nerd of Mathematics and Computer Science.
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
