Valgrind Process Details
back to processes overview
/home1/jenkins/workspace/ProjectX_Nightly/PX_ARC/release_clang/buildnode/reynolds/platforms/release_clang/src/Grid/PXUnitCutGrids_PXU (process 18385)
--tool=memcheck --leak-check=yes --show-leak-kinds=all --errors-for-leak-kinds=all --num-callers=50 --error-exitcode=1 --gen-suppressions=all --suppressions=/home1/jenkins/workspace/ProjectX_Nightly/PX_ARC/release_clang/buildnode/reynolds/src/Test/valgrind.supp --suppressions=/home1/jenkins/workspace/ProjectX_Nightly/PX_ARC/release_clang/buildnode/reynolds/src/Test/Ubuntu.supp --track-origins=yes --xml=yes --xml-file=/home1/jenkins/workspace/ProjectX_Nightly/PX_ARC/release_clang/buildnode/reynolds/platforms/release_clang/valgrind.%p.memcheck.xml
|
|
18383 |
|
Memory Leaks (still reachable):
A start-pointer or chain of start-pointers to the block is found. Since the block is still pointed at, the programmer could, at least in principle, have freed it before program exit. (Valgrind Manual)
|
0x277 | 6 bytes in 1 blocks are still reachable in loss record 631 of 3,370 |
0x2cd | 7 bytes in 1 blocks are still reachable in loss record 717 of 3,370 |
0x2ce | 7 bytes in 1 blocks are still reachable in loss record 718 of 3,370 |
0x347 | 8 bytes in 1 blocks are still reachable in loss record 839 of 3,370 |
0x348 | 8 bytes in 1 blocks are still reachable in loss record 840 of 3,370 |
0x349 | 8 bytes in 1 blocks are still reachable in loss record 841 of 3,370 |
0x34a | 8 bytes in 1 blocks are still reachable in loss record 842 of 3,370 |
0x4df | 16 bytes in 1 blocks are still reachable in loss record 1,247 of 3,370 |
0x4e0 | 16 bytes in 1 blocks are still reachable in loss record 1,248 of 3,370 |
0x4e1 | 16 bytes in 1 blocks are still reachable in loss record 1,249 of 3,370 |
0x4e2 | 16 bytes in 1 blocks are still reachable in loss record 1,250 of 3,370 |
0x4e3 | 16 bytes in 1 blocks are still reachable in loss record 1,251 of 3,370 |
0x4e4 | 16 bytes in 1 blocks are still reachable in loss record 1,252 of 3,370 |
0x4e5 | 16 bytes in 1 blocks are still reachable in loss record 1,253 of 3,370 |
0x5a0 | 24 bytes in 1 blocks are still reachable in loss record 1,440 of 3,370 |
0x5a1 | 24 bytes in 1 blocks are still reachable in loss record 1,441 of 3,370 |
0x5a2 | 24 bytes in 1 blocks are still reachable in loss record 1,442 of 3,370 |
0x675 | 32 bytes in 1 blocks are still reachable in loss record 1,653 of 3,370 |
0x676 | 32 bytes in 1 blocks are still reachable in loss record 1,654 of 3,370 |
0x677 | 32 bytes in 1 blocks are still reachable in loss record 1,655 of 3,370 |
0xb32 | 88 bytes in 1 blocks are still reachable in loss record 2,866 of 3,370 |
0xb33 | 88 bytes in 1 blocks are still reachable in loss record 2,867 of 3,370 |
0xb34 | 88 bytes in 1 blocks are still reachable in loss record 2,868 of 3,370 |
0xc5d | 256 bytes in 1 blocks are still reachable in loss record 3,165 of 3,370 |
0xca2 | 512 bytes in 1 blocks are still reachable in loss record 3,234 of 3,370 |
0xca3 | 512 bytes in 1 blocks are still reachable in loss record 3,235 of 3,370 |
0xca9 | 688 bytes in 1 blocks are still reachable in loss record 3,241 of 3,370 |
0xcaa | 688 bytes in 1 blocks are still reachable in loss record 3,242 of 3,370 |
0xcab | 688 bytes in 1 blocks are still reachable in loss record 3,243 of 3,370 |
0xcd2 | 1,040 bytes in 1 blocks are still reachable in loss record 3,282 of 3,370 |
0xcd3 | 1,040 bytes in 1 blocks are still reachable in loss record 3,283 of 3,370 |
0xcd4 | 1,040 bytes in 1 blocks are still reachable in loss record 3,284 of 3,370 |