1 2 3HEAP SUMMARY: 4 in use at exit: ... bytes in ... blocks 5 total heap usage: ... allocs, ... frees, ... bytes allocated 6 7Block 0x..........0x........ overlaps with block 0x..........0x........ 8Blocks allocation contexts: 9 ... 10 11 ... 12This is usually caused by using VALGRIND_MALLOCLIKE_BLOCK in an inappropriate way. 13 14Memcheck: mc_leakcheck.c:... (vgMemCheck_detect_memory_leaks): the 'impossible' happened. 15 16host stacktrace: 17 ... 18 19sched status: 20 running_tid=1 21 22 23Note: see also the FAQ in the source distribution. 24It contains workarounds to several common problems. 25In particular, if Valgrind aborted or crashed after 26identifying problems in your program, there's a good chance 27that fixing those problems will prevent Valgrind aborting or 28crashing, especially if it happened in m_mallocfree.c. 29 30If that doesn't help, please report this bug to: www.valgrind.org 31 32In the bug report, send all the above text, the valgrind 33version, and what OS and version you are using. Thanks. 34 35