Re: malloc in glibc 2.3.1

[Wolfram Gloger]

> Using valgrind the program has executed sucessfully, so now I really don't
> know where the problem is :-).

Actually, _no_, valgrind has reported many serious errors, I just
quote the first one from your log.gz:

==28126== Invalid write of size 4
==28126==    at 0x8054867: find_blocks (cache.c:566)
==28126==    by 0x805432B: cache_read (cache.c:149)
==28126==    by 0x8053DB3: main (test.c:30)
==28126==    by 0x40268B34: __libc_start_main (in /lib/libc-2.3.1.so)
==28126==    Address 0x42C6B2DC is 200 bytes inside a block of size 201 alloc'd
==28126==    at 0x4003DA4E: malloc (vg_clientfuncs.c:100)
==28126==    by 0x8054841: find_blocks (cache.c:562)
==28126==    by 0x805432B: cache_read (cache.c:149)
==28126==    by 0x8053DB3: main (test.c:30)
==28126== 

You need to fix _all_ those out-of-bounds writes and reads before you
can even suspect a bug in malloc.

Regards,
Wolfram.