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.

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

fixed few potential memory/resource leaks #803

Merged
merged 1 commit into from
May 13, 2019

Conversation

slyshykO
Copy link
Collaborator

also few cppcheck warnings

also few cppcheck warnings
@xor-gate xor-gate merged commit d040db5 into stlink-org:master May 13, 2019
@xor-gate xor-gate added this to the Next milestone May 13, 2019
@xor-gate
Copy link
Member

Thanks @slyshykO we should also have some sort of scan-build in our CI system where static analysis with Clang checks for errors. E.g https://stackoverflow.com/questions/31177633/how-to-find-memory-leaks-with-clang

@Nightwalker-87 Nightwalker-87 removed this from the General milestone Feb 21, 2020
@Nightwalker-87 Nightwalker-87 added this to the v1.6.0 milestone Feb 21, 2020
@Nightwalker-87 Nightwalker-87 self-assigned this Feb 21, 2020
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Apr 27, 2020
@slyshykO slyshykO deleted the fix-memory branch June 19, 2020 06:12
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[gdb] target state locked in "running" after step instruction with st-util and gdb
3 participants