-
Notifications
You must be signed in to change notification settings - Fork 3k
cellular: valgrind defect fix #10269
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
Conversation
@TeemuKultala, thank you for your changes. |
@jarvte could you please re-approve (your approval seems to have been cleared, although I don't see any subsequent changes) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the commit message is not sufficient for this fix. please add more details - what issues is this fixing and how. The only relevant change I can see in the at_cellulardevicetest.cpp
but the rest of changes are not clear to me what they are fixing.
How did you run valgrind? |
at_cellulardevicetest.cpp: fix potential memory leak at_cellularsmstest.cpp: fix potential memory leak, uninitialized memory conditional athandlertest.cpp: fix potential memory leak, uninitialized memory conditional, uninitialized memory read ATHandler_stub.cpp, ATHandler_stub.h: fix potential memory leak, uninitialized memory conditional
Discovered valgrind defect types for each file added to the commit message. How the defects are fixed can be seen by inspecting the changes. Valgrind test was ran this way: After this the report is available in Testing/current_date_time folder |
Test run: SUCCESSSummary: 1 of 1 test jobs passed |
Description
This fixes cellular Valgrind memtest defects. Tested with unit tests. cellulardevicetest.cpp valgrind problem is going to be addressed separately
Pull request type
Reviewers
@jarvte @mirelachirica