Closed znichola closed 1 year ago
==4419== LEAK SUMMARY: ==4419== definitely lost: 0 bytes in 0 blocks ==4419== indirectly lost: 0 bytes in 0 blocks ==4419== possibly lost: 0 bytes in 0 blocks ==4419== still reachable: 211,940 bytes in 368 blocks ==4419== suppressed: 0 bytes in 0 blocks ... ==4397== HEAP SUMMARY: ==4397== in use at exit: 211,735 bytes in 360 blocks ==4397== total heap usage: 6,382 allocs, 6,022 frees, 1,682,477 bytes allocated ==4397== ==4397== Searching for pointers to 360 not-freed blocks ==4397== Checked 312,536 bytes ... #and more
usage make sure fsanitize=address is off but the -g is on
fsanitize=address
-g
valgrind --leak-check=full \ --show-leak-kinds=all \ --track-origins=yes \ --log-file=valgrind-out.txt \ ./minishell
installation
apt install valgrind
will add it to the docker image, so we can more easily test, maybe the option to launch the leaks check with a makefile rule
closing as this is more informational
usage make sure
fsanitize=address
is off but the-g
is oninstallation
will add it to the docker image, so we can more easily test, maybe the option to launch the leaks check with a makefile rule