If this is not enough information to find where the memory leak is, we can rerun valgrind with --leak-check=full.