As the new valgrind can show alloc and free callstack for use after free
of normal heap memory I thought this should also work for memory pools.
There are even more callstacks that are known.
For the testcase clireq_nofill.c
==26295== Invalid read of size 1
==26295== at 0x8048780: main (clireq_nofill.c:23)
==26295== Address 0x4034028 is 0 bytes inside a recently re-allocated block of size 40 alloc'd
==26295== at 0x4009D98: malloc (vg_replace_malloc.c:270)
==26295== by 0x804860E: main (clireq_nofill.c:16)
==26693== Invalid read of size 1
==26693== at 0x8048780: main (clireq_nofill.c:23)
==26693== Address 0x4034028 is 0 bytes inside a recently re-allocated block of size 40 alloc'd
==26693== at 0x40093A1: malloc (vg_replace_malloc.c:291)
==26693== by 0x804860E: main (clireq_nofill.c:16)
==26693== inner block was freed at
==26693== at 0x804876B: main (clireq_nofill.c:22)
==26693== inner block was allocated at
==26693== at 0x80486E0: main (clireq_nofill.c:20)
For this I only wonder about how to name the different callstacks.
Get latest updates about Open Source Projects, Conferences and News.