Re: [gtk-list] Re: how can I trust glib when it has so many memleaks?
- From: Joe Pfeiffer <pfeiffer cs nmsu edu>
- To: gtk-list redhat com
- Subject: Re: [gtk-list] Re: how can I trust glib when it has so many memleaks?
- Date: Wed, 17 Mar 1999 22:44:13 -0700
On Thu, 18 Mar 1999, Ionutz Borcoman wrote:
> This is INSANE ! It's like giving a kid a posisoned candy :-(
> How can I differentiate what ccmalloc sais for glib comparred with what
> it says for my program ?
Well, the glib memory caching speeds dynamic data structures up by a large
factor. If that interferes with ccmalloc, well, such is life.
Ionutz has a really good point here -- finding memory leaks is hard
enough without having libraries that hide them. Hmmm... I haven't
looked at glib's implementation, but if it has a memory
allocation/deallocation package built into it (which I'd sort of
expect), it ought to be reasonably straightforward to do something
like either compile this with its current implementation or as a
wrapper around malloc/free...
Joseph J. Pfeiffer, Jr., Ph.D. Phone -- (505) 646-1605
Department of Computer Science FAX -- (505) 646-1002
New Mexico State University http://www.cs.nmsu.edu/~pfeiffer
] [Thread Prev