We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
looks like there are a few memory leaks/invalid reads that should be addressed:
$ valgrind ./test --leak-check=full [ ... ] ==5700== ==5700== HEAP SUMMARY: ==5700== in use at exit: 566 bytes in 55 blocks ==5700== total heap usage: 116 allocs, 61 frees, 1,067 bytes allocated ==5700== [ ... ] ==5700== LEAK SUMMARY: ==5700== definitely lost: 566 bytes in 55 blocks ==5700== indirectly lost: 0 bytes in 0 blocks ==5700== possibly lost: 0 bytes in 0 blocks ==5700== still reachable: 0 bytes in 0 blocks ==5700== suppressed: 0 bytes in 0 blocks ==5700== ==5700== For counts of detected and suppressed errors, rerun with: -v ==5700== ERROR SUMMARY: 95 errors from 22 contexts (suppressed: 2 from 2)
here's the full valgrind report that shows what's happening in more detail.
The text was updated successfully, but these errors were encountered:
Ouch! Thanks a lot, will take a look asap!
Sorry, something went wrong.
fix(#6)
8c011f2
This should be fixed now. See: 8c011f2
awesome!
No branches or pull requests
looks like there are a few memory leaks/invalid reads that should be addressed:
here's the full valgrind report that shows what's happening in more detail.
The text was updated successfully, but these errors were encountered: