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