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 18386)
--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)
|
0x268 | 6 bytes in 1 blocks are still reachable in loss record 616 of 3,310 |
0x2bd | 7 bytes in 1 blocks are still reachable in loss record 701 of 3,310 |
0x2be | 7 bytes in 1 blocks are still reachable in loss record 702 of 3,310 |
0x334 | 8 bytes in 1 blocks are still reachable in loss record 820 of 3,310 |
0x335 | 8 bytes in 1 blocks are still reachable in loss record 821 of 3,310 |
0x336 | 8 bytes in 1 blocks are still reachable in loss record 822 of 3,310 |
0x337 | 8 bytes in 1 blocks are still reachable in loss record 823 of 3,310 |
0x4c7 | 16 bytes in 1 blocks are still reachable in loss record 1,223 of 3,310 |
0x4c8 | 16 bytes in 1 blocks are still reachable in loss record 1,224 of 3,310 |
0x4c9 | 16 bytes in 1 blocks are still reachable in loss record 1,225 of 3,310 |
0x4ca | 16 bytes in 1 blocks are still reachable in loss record 1,226 of 3,310 |
0x4cb | 16 bytes in 1 blocks are still reachable in loss record 1,227 of 3,310 |
0x4cc | 16 bytes in 1 blocks are still reachable in loss record 1,228 of 3,310 |
0x4cd | 16 bytes in 1 blocks are still reachable in loss record 1,229 of 3,310 |
0x586 | 24 bytes in 1 blocks are still reachable in loss record 1,414 of 3,310 |
0x587 | 24 bytes in 1 blocks are still reachable in loss record 1,415 of 3,310 |
0x588 | 24 bytes in 1 blocks are still reachable in loss record 1,416 of 3,310 |
0x656 | 32 bytes in 1 blocks are still reachable in loss record 1,622 of 3,310 |
0x657 | 32 bytes in 1 blocks are still reachable in loss record 1,623 of 3,310 |
0x658 | 32 bytes in 1 blocks are still reachable in loss record 1,624 of 3,310 |
0xaf7 | 88 bytes in 1 blocks are still reachable in loss record 2,807 of 3,310 |
0xaf8 | 88 bytes in 1 blocks are still reachable in loss record 2,808 of 3,310 |
0xaf9 | 88 bytes in 1 blocks are still reachable in loss record 2,809 of 3,310 |
0xc22 | 256 bytes in 1 blocks are still reachable in loss record 3,106 of 3,310 |
0xc66 | 512 bytes in 1 blocks are still reachable in loss record 3,174 of 3,310 |
0xc67 | 512 bytes in 1 blocks are still reachable in loss record 3,175 of 3,310 |
0xc6d | 688 bytes in 1 blocks are still reachable in loss record 3,181 of 3,310 |
0xc6e | 688 bytes in 1 blocks are still reachable in loss record 3,182 of 3,310 |
0xc6f | 688 bytes in 1 blocks are still reachable in loss record 3,183 of 3,310 |
0xc96 | 1,040 bytes in 1 blocks are still reachable in loss record 3,222 of 3,310 |
0xc97 | 1,040 bytes in 1 blocks are still reachable in loss record 3,223 of 3,310 |
0xc98 | 1,040 bytes in 1 blocks are still reachable in loss record 3,224 of 3,310 |