Skip to content

Static-code analysis C algorithm #16

@DavidGarfinkle

Description

@DavidGarfinkle

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions