tests/malloc_thread_safety: new test#15598
Closed
maribu wants to merge 1 commit intoRIOT-OS:masterfrom
Closed
Conversation
maribu
requested review from
MichelRottleuthner,
aabadie,
fjmolinas,
leandrolanzieri,
miri64 and
smlng
as code owners
maribu
added
Area: tests
This test checks whether calling malloc in more than one thread is safe.
maribu
force-pushed
the
malloc-thread-safety
branch
from
51fcee0 to
b60a343
Compare
Member
Author
|
Test result is as it should: The ARM board fails, the ESP platforms have custom guards in place, so the ESP32 board passes. |
Member
Author
|
Test merged with the fix. Hence, this PR is no longer needed. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Contribution description
This PR adds a test application to confirm an issue with multithreaded use of standard C library functions, specifically
malloc()andfree().Testing procedure
The automated tests should fail for all platforms but AVR and ESP32/ESP8266: AVR has special wrapper for calls to
malloc()andfree()to prevent memory corruptions. ESP* have implement the locking hooks expected by newlib.Issues/PRs references
Helpful for e.g. testing #8619