Fix: Use malloc and free for cv_stack to avoid dangling pointer warning #1417
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.
Before the change, running
make cf2_defconfig
andmake clean
generated warnings about dangling pointers in the configuration process.After the update, the command completes without any warnings.
The changes in this PR shouldn't practically change anything except acknowledge that we are responsible for cv_stack. The function in question is called during recursive dependency checking. I tested this PR by deliberately introducing recursive dependency in kconfig.