Re: [gtk-list] Re: how can I trust glib when it has so many memleaks?

[Joe Pfeiffer <pfeiffer cs nmsu edu>]

   > 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...

   It doesn't look to me like that would work but I'm not an expert. You
   might look at gslist.c for an example.

I wish I had time to look in detail...  at a first glance it does look
possible...

   You could probably free all the memory en masse at program exit but there
   was some reason I don't remember why that isn't being done. 

Even this would help.
-- 
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