Old valrgind for theclam/stripe

gistfile1.txt

[alex@zmachine stripe]$ valgrind --leak-check=full ./stripe -r ~/Downloads/gtp-u.pcap -w foo.bla
==23053== Memcheck, a memory error detector
==23053== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==23053== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==23053== Command: ./stripe -r /home/alex/Downloads/gtp-u.pcap -w foo.bla
==23053== 

Reassembling...

Decapsulating...

102 frames processed.
==23053== 
==23053== HEAP SUMMARY:
==23053==     in use at exit: 64 bytes in 2 blocks
==23053==   total heap usage: 214 allocs, 212 frees, 30,024 bytes allocated
==23053== 
==23053== 32 bytes in 1 blocks are definitely lost in loss record 1 of 2
==23053==    at 0x4C29BCF: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==23053==    by 0x40250B: parse_pcap (stripe.c:378)
==23053==    by 0x402AE6: main (stripe.c:529)
==23053== 
==23053== 32 bytes in 1 blocks are definitely lost in loss record 2 of 2
==23053==    at 0x4C29BCF: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==23053==    by 0x40250B: parse_pcap (stripe.c:378)
==23053==    by 0x402B17: main (stripe.c:531)
==23053== 
==23053== LEAK SUMMARY:
==23053==    definitely lost: 64 bytes in 2 blocks
==23053==    indirectly lost: 0 bytes in 0 blocks
==23053==      possibly lost: 0 bytes in 0 blocks
==23053==    still reachable: 0 bytes in 0 blocks
==23053==         suppressed: 0 bytes in 0 blocks
==23053== 
==23053== For counts of detected and suppressed errors, rerun with: -v
==23053== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)

Sorry, had a copy&paste error, had to update this.