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

[Owen Taylor <otaylor at redhat dot com>]

On Sun, 2003-07-20 at 09:14, Martin Schlemmer wrote:
> 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.

OK, that makes it very likely that you have bad memory.
If you have crashes with software that happens for nobody
else, then look at your hardware.

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

I bet it's just whatever is doing the most malloc traffic.

Regards,
						Owen