Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Static-code analysis C algorithm #16

Open
DavidGarfinkle opened this issue Aug 15, 2019 · 0 comments
Open

Static-code analysis C algorithm #16

DavidGarfinkle opened this issue Aug 15, 2019 · 0 comments

Comments

@DavidGarfinkle
Copy link
Collaborator

The C code was never formally checked for memory leaks
This could lead to unstable behaviour in the future
I should run a memory management tool like http://www.valgrind.org/ to defensively erase those errors before they crash the component in production
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DavidGarfinkle