vt-cs-projects / c08_gis_system / test / grading / vgrind_issues.txt
vgrind_issues.txt
Raw
Valgrind issues:
==899561==     in use at exit: 346,639 bytes in 30,577 blocks
==899561==   total heap usage: 79,291 allocs, 48,714 frees, 3,665,307 bytes allocated
==899561== 20 bytes in 4 blocks are definitely lost in loss record 14 of 68
==899561== 20 bytes in 4 blocks are definitely lost in loss record 15 of 68
==899561== 24 bytes in 4 blocks are definitely lost in loss record 16 of 68
==899561== 24 bytes in 4 blocks are definitely lost in loss record 17 of 68
==899561== 28 bytes in 4 blocks are definitely lost in loss record 20 of 68
==899561== 28 bytes in 4 blocks are definitely lost in loss record 21 of 68
==899561== 28 bytes in 4 blocks are definitely lost in loss record 22 of 68
==899561== 28 bytes in 4 blocks are definitely lost in loss record 23 of 68
==899561== 30 bytes in 10 blocks are definitely lost in loss record 29 of 68
==899561== 32 bytes in 4 blocks are definitely lost in loss record 30 of 68
==899561== 32 bytes in 4 blocks are definitely lost in loss record 31 of 68
==899561== 36 bytes in 4 blocks are definitely lost in loss record 32 of 68
==899561== 36 bytes in 4 blocks are definitely lost in loss record 33 of 68
==899561== 50 bytes in 10 blocks are definitely lost in loss record 35 of 68
==899561== 60 bytes in 5 blocks are definitely lost in loss record 36 of 68
==899561== 60 bytes in 10 blocks are definitely lost in loss record 37 of 68
==899561== 70 bytes in 10 blocks are definitely lost in loss record 41 of 68
==899561== 77 bytes in 5 blocks are definitely lost in loss record 42 of 68
==899561== 80 bytes in 10 blocks are definitely lost in loss record 43 of 68
==899561== 84 bytes in 6 blocks are definitely lost in loss record 44 of 68
==899561== 90 bytes in 10 blocks are definitely lost in loss record 45 of 68
==899561== 92 (64 direct, 28 indirect) bytes in 4 blocks are definitely lost in loss record 46 of 68
==899561== 92 (64 direct, 28 indirect) bytes in 4 blocks are definitely lost in loss record 47 of 68
==899561== 95 bytes in 8 blocks are definitely lost in loss record 48 of 68
==899561== 96 bytes in 8 blocks are definitely lost in loss record 49 of 68
==899561== 110 bytes in 6 blocks are definitely lost in loss record 50 of 68
==899561== 136 bytes in 20 blocks are definitely lost in loss record 51 of 68
==899561== 139 bytes in 20 blocks are definitely lost in loss record 52 of 68
==899561== 190 bytes in 28 blocks are definitely lost in loss record 54 of 68
==899561== 193 bytes in 28 blocks are definitely lost in loss record 55 of 68
==899561== 339 bytes in 50 blocks are definitely lost in loss record 56 of 68
==899561== 462 (320 direct, 142 indirect) bytes in 4 blocks are definitely lost in loss record 57 of 68
==899561== 462 (320 direct, 142 indirect) bytes in 4 blocks are definitely lost in loss record 58 of 68
==899561== 499 bytes in 1 blocks are definitely lost in loss record 59 of 68
==899561== 1,162 (800 direct, 362 indirect) bytes in 10 blocks are definitely lost in loss record 61 of 68
==899561== 1,530 (720 direct, 810 indirect) bytes in 10 blocks are definitely lost in loss record 62 of 68
==899561== 15,012 bytes in 5,001 blocks are definitely lost in loss record 63 of 68
==899561== 35,011 bytes in 5,001 blocks are definitely lost in loss record 64 of 68
==899561== 35,011 bytes in 5,001 blocks are definitely lost in loss record 65 of 68
==899561== 80,016 bytes in 5,001 blocks are definitely lost in loss record 66 of 68
==899561== 82,522 bytes in 5,001 blocks are definitely lost in loss record 67 of 68
==899561== 92,518 bytes in 5,000 blocks are definitely lost in loss record 68 of 68
==899561==    definitely lost: 345,112 bytes in 30,334 blocks
Invalid reads: 0
Invalid writes: 0
Uses of uninitialized values: 0