Dont free the kb_path twice. #499
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The functions calling g_strdup (kb_path) already take care of free()'ing the string, as well as delete once the kb is deleted.
jjnicola
added
the
backport-to-main
ArnoStiefvater
approved these changes
May 17, 2021
ArnoStiefvater
added a commit
that referenced
this pull request
May 17, 2021
Dont free the kb_path twice. (backport #499)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What:
Dont free the kb_path twice.
Why:
The functions calling g_strdup (kb_path) already take care of free()'ing the string, as well as delete once the kb is deleted.
How:
Kill redis and call openvas in the console.
You can run
valgrind openvasand check it.Checklist: