ci(memory_leaks): Fix CI valgrind check and resolve function memory leaks #121
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.
Description
This pull request includes several important changes to memory management and testing procedures in the codebase. The changes focus on improving the handling of function parameters and enhancing the reliability of the test suite.
Memory management improvements:
ast.c
: Added a call tofree_parameters
to ensure all function parameters are properly freed infree_ast
.ast.c
: Added a call toSAFE_FREE
for variables inenter_function_scope
to prevent memory leaks.ast.c
: Added a call toreverse_parameter_list
inenter_function_scope
to ensure the parameter list is in the correct order.Testing enhancements:
run_valgrind_tests.sh
: Added a check for Valgrind errors and an exit command to stop the script if Valgrind detects any issues. This ensures that memory leaks and errors are caught during testing.Related Issue
Fixes #<issue_number>
Type of Change
Checklist