tests: posix: pthread: init pthread_attr_t on each iteration #57403
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.
The
test_pthread_descriptor_leaktest was causing a kernel panic on some platforms. Initially, it was not clear why.The usual cases were examined - race conditions, stack sizes, etc. Still no luck.
As it turns out, recycling a thread stack (or at least the
pthread_attr_t) in-place does not work on some platforms, and we need to reinitialize thepthread_attr_tand set set the stack property again prior to callingpthread_create().Fixes #56163
Tested with:
west build -p always -b qemu_cortex_r5 -t run tests/posix/common \ -- -DCONFIG_TICKLESS_KERNEL=n -DCONFIG_NEWLIB_LIBC=y