blob: 21ef2df98e422cdf0d41494278903397f8039999 [file] [log] [blame]
philippe21fcbb72012-09-14 21:10:15 +00001
2All heap blocks were freed -- no leaks are possible
3
4expecting no leaks
5LEAK SUMMARY:
6 definitely lost: 0 bytes in 0 blocks
7 indirectly lost: 0 bytes in 0 blocks
8 possibly lost: 0 bytes in 0 blocks
Elliott Hughesed398002017-06-21 14:41:24 -07009 still reachable: 201,000 bytes in 2 blocks
philippe21fcbb72012-09-14 21:10:15 +000010 suppressed: 0 bytes in 0 blocks
11Reachable blocks (those to which a pointer was found) are not shown.
philippe2193a7c2012-12-08 17:54:16 +000012To see them, rerun with: --leak-check=full --show-leak-kinds=all
philippe21fcbb72012-09-14 21:10:15 +000013
14expecting a leak
151,000 bytes in 1 blocks are definitely lost in loss record ... of ...
16 at 0x........: malloc (vg_replace_malloc.c:...)
Elliott Hughesed398002017-06-21 14:41:24 -070017 by 0x........: f (leak-segv-jmp.c:271)
18 by 0x........: main (leak-segv-jmp.c:346)
philippe21fcbb72012-09-14 21:10:15 +000019
20LEAK SUMMARY:
21 definitely lost: 1,000 bytes in 1 blocks
22 indirectly lost: 0 bytes in 0 blocks
23 possibly lost: 0 bytes in 0 blocks
Elliott Hughesed398002017-06-21 14:41:24 -070024 still reachable: 200,000 bytes in 1 blocks
philippe21fcbb72012-09-14 21:10:15 +000025 suppressed: 0 bytes in 0 blocks
26Reachable blocks (those to which a pointer was found) are not shown.
philippe2193a7c2012-12-08 17:54:16 +000027To see them, rerun with: --leak-check=full --show-leak-kinds=all
philippe21fcbb72012-09-14 21:10:15 +000028
29mprotect result 0
30expecting a leak again
311,000 bytes in 1 blocks are definitely lost in loss record ... of ...
32 at 0x........: malloc (vg_replace_malloc.c:...)
Elliott Hughesed398002017-06-21 14:41:24 -070033 by 0x........: f (leak-segv-jmp.c:271)
34 by 0x........: main (leak-segv-jmp.c:346)
philippe7a76f4b2013-10-06 21:23:04 +000035
36LEAK SUMMARY:
37 definitely lost: 1,000 bytes in 1 blocks
38 indirectly lost: 0 bytes in 0 blocks
39 possibly lost: 0 bytes in 0 blocks
Elliott Hughesed398002017-06-21 14:41:24 -070040 still reachable: 200,000 bytes in 1 blocks
philippe7a76f4b2013-10-06 21:23:04 +000041 suppressed: 0 bytes in 0 blocks
42Reachable blocks (those to which a pointer was found) are not shown.
43To see them, rerun with: --leak-check=full --show-leak-kinds=all
44
45full mprotect result 0
46expecting a leak again after full mprotect
471,000 bytes in 1 blocks are definitely lost in loss record ... of ...
48 at 0x........: malloc (vg_replace_malloc.c:...)
Elliott Hughesed398002017-06-21 14:41:24 -070049 by 0x........: f (leak-segv-jmp.c:271)
50 by 0x........: main (leak-segv-jmp.c:346)
philippe21fcbb72012-09-14 21:10:15 +000051
52LEAK SUMMARY:
53 definitely lost: 1,000 bytes in 1 blocks
54 indirectly lost: 0 bytes in 0 blocks
55 possibly lost: 0 bytes in 0 blocks
Elliott Hughesed398002017-06-21 14:41:24 -070056 still reachable: 200,000 bytes in 1 blocks
philippe21fcbb72012-09-14 21:10:15 +000057 suppressed: 0 bytes in 0 blocks
58Reachable blocks (those to which a pointer was found) are not shown.
philippe2193a7c2012-12-08 17:54:16 +000059To see them, rerun with: --leak-check=full --show-leak-kinds=all
philippe21fcbb72012-09-14 21:10:15 +000060
philippeb5a02e72015-10-22 19:14:30 +000061mprotect result 0
62expecting heuristic not to crash after full mprotect
631,000 bytes in 1 blocks are definitely lost in loss record ... of ...
64 at 0x........: malloc (vg_replace_malloc.c:...)
Elliott Hughesed398002017-06-21 14:41:24 -070065 by 0x........: f (leak-segv-jmp.c:271)
66 by 0x........: main (leak-segv-jmp.c:346)
philippeb5a02e72015-10-22 19:14:30 +000067
Elliott Hughesed398002017-06-21 14:41:24 -070068200,000 bytes in 1 blocks are possibly lost in loss record ... of ...
philippeb5a02e72015-10-22 19:14:30 +000069 at 0x........: calloc (vg_replace_malloc.c:...)
Elliott Hughesed398002017-06-21 14:41:24 -070070 by 0x........: f (leak-segv-jmp.c:318)
71 by 0x........: main (leak-segv-jmp.c:346)
philippeb5a02e72015-10-22 19:14:30 +000072
73LEAK SUMMARY:
74 definitely lost: 1,000 bytes in 1 blocks
75 indirectly lost: 0 bytes in 0 blocks
Elliott Hughesed398002017-06-21 14:41:24 -070076 possibly lost: 200,000 bytes in 1 blocks
77 still reachable: 200,000 bytes in 1 blocks
philippeb5a02e72015-10-22 19:14:30 +000078 suppressed: 0 bytes in 0 blocks
79Reachable blocks (those to which a pointer was found) are not shown.
80To see them, rerun with: --leak-check=full --show-leak-kinds=all
81
philippe21fcbb72012-09-14 21:10:15 +000082finished
83LEAK SUMMARY:
84 definitely lost: 1,000 bytes in 1 blocks
85 indirectly lost: 0 bytes in 0 blocks
Elliott Hughesed398002017-06-21 14:41:24 -070086 possibly lost: 200,000 bytes in 1 blocks
87 still reachable: 200,000 bytes in 1 blocks
philippe21fcbb72012-09-14 21:10:15 +000088 suppressed: 0 bytes in 0 blocks
89Rerun with --leak-check=full to see details of leaked memory
90
91leaked: 1000 bytes in 1 blocks
Elliott Hughesed398002017-06-21 14:41:24 -070092dubious: 200000 bytes in 1 blocks
93reachable: 200000 bytes in 1 blocks
philippe21fcbb72012-09-14 21:10:15 +000094suppressed: 0 bytes in 0 blocks
95
96HEAP SUMMARY:
Elliott Hughesed398002017-06-21 14:41:24 -070097 in use at exit: 401,000 bytes in 3 blocks
98 total heap usage: 3 allocs, 0 frees, 401,000 bytes allocated
philippe21fcbb72012-09-14 21:10:15 +000099
100For a detailed leak analysis, rerun with: --leak-check=full
101
102For counts of detected and suppressed errors, rerun with: -v
philippeb5a02e72015-10-22 19:14:30 +0000103ERROR SUMMARY: 5 errors from 5 contexts (suppressed: 0 from 0)