Random failures when calling free()/malloc()

[Martin Schlemmer]

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

I wont argue here, what makes it just a bit more difficult, is that it
works fine with a older glibc :/

> 'export MALLOC_CHECK_=2' valgrind, or even the good old standby of
> Electric Fence should help you track it down.
> 

Once again, thanks for the suggestion, but valgrind do not compile under
nptl =).  If I get time in a week or two, I will try to get it to
compile.  Currently busy trying to check with MALLOC_CHECK_=2, thanks.


Regards,

-- 

Martin Schlemmer



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20030720/4f2fb8b2/attachment.sig>