Closed ghost closed 8 months ago
Checking build/examples/CalcQt/QtTestCalculatorQtSteps with valgrind --verbose shows the following report:
build/examples/CalcQt/QtTestCalculatorQtSteps
valgrind --verbose
. . . ==16602== HEAP SUMMARY: ==16602== in use at exit: 2,188,522 bytes in 22,591 blocks ==16602== total heap usage: 1,804,795 allocs, 1,782,204 frees, 167,480,649 bytes allocated ==16602== ==16602== Searching for pointers to 21,920 not-freed blocks ==16602== Checked 20,706,856 bytes ==16602== ==16602== LEAK SUMMARY: ==16602== definitely lost: 25,956 bytes in 704 blocks ==16602== indirectly lost: 12,958 bytes in 77 blocks ==16602== possibly lost: 3,400 bytes in 32 blocks ==16602== still reachable: 2,063,952 bytes in 21,107 blocks ==16602== of which reachable via heuristic: ==16602== length64 : 4,872 bytes in 81 blocks ==16602== newarray : 2,064 bytes in 49 blocks ==16602== suppressed: 0 bytes in 0 blocks ==16602== Rerun with --leak-check=full to see details of leaked memory ==16602== ==16602== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==16602== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
$ uname -srmo
Linux 4.19.9-arch1-1-ARCH x86_64 GNU/Linux
configure.log build.log valgrind-qtsteps.log
Only found memory leaks within Qt, not cucumber-cpp.
Summary
Checking
build/examples/CalcQt/QtTestCalculatorQtSteps
withvalgrind --verbose
shows the following report:Your Environment
$ uname -srmo
saysLinux 4.19.9-arch1-1-ARCH x86_64 GNU/Linux
Logs
configure.log build.log valgrind-qtsteps.log