Project

Profile

Help

RE: Possible memory leaks » valgrind-output-SaxonCValidator.txt

Paul Greve, 2025-01-27 12:13

 

[tacds@localhost Debug]$ valgrind ./SaxonCValidator
==3493== Memcheck, a memory error detector
==3493== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.
==3493== Using Valgrind-3.24.0 and LibVEX; rerun with -h for copyright info
==3493== Command: ./SaxonCValidator
==3493==
!!!Hello World!!!
Validation successful!
==3493==
==3493== HEAP SUMMARY:
==3493== in use at exit: 49,792 bytes in 4 blocks
==3493== total heap usage: 68 allocs, 64 frees, 199,682 bytes allocated
==3493==
==3493== LEAK SUMMARY:
==3493== definitely lost: 0 bytes in 0 blocks
==3493== indirectly lost: 0 bytes in 0 blocks
==3493== possibly lost: 288 bytes in 1 blocks
==3493== still reachable: 49,504 bytes in 3 blocks
==3493== suppressed: 0 bytes in 0 blocks
==3493== Rerun with --leak-check=full to see details of leaked memory
==3493==
==3493== For lists of detected and suppressed errors, rerun with: -s
==3493== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
[tacds@localhost Debug]$
(1-1/2)