Re: Random failures when calling free()/malloc()

[Martin Schlemmer <azarah at gentoo dot org>]

On Sat, 2003-07-19 at 20:23, Owen Taylor wrote:

> 
> This is classic memory corruption, probably a double free somewhere
> in your application.  It's certainly not libc, and unlikely
> to be GLib/GTK+ either... memory corruption failures are frequently
> not 'local' - a bug in one place will cause a crash somewhere 
> else.
> 

Btw, its not really 'my' application.  It does it with some of the
tests from glib-2.2.2 as well.

This is where I want to ask something - are the  any known issues
with glib-2.2.* and latest cvs glibc+nptl ?  Most of the issues I
see have a g_free/g_new/g_malloc in there ...  glib-1.2* stuff is
fine though ...


Thanks,

-- 

Martin Schlemmer

Attachment: signature.asc
Description: This is a digitally signed message part