core/thread: always use THREAD_CREATE_STACKTEST when DEVELHELP is enabled #20450
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
We already create every thread with
THREAD_CREATE_STACKTEST
.If someone creates a thread without it,
ps
output is weird (all stack is marked as used) and the overhead is only at thread creation and only whenDEVELHELP
is set.Remove the flag (but keep the define to not break apps) since in all those years, not a single use-case has been found for creating a thread without
THREAD_CREATE_STACKTEST
.Testing procedure
ps
still uses the stack usage withDEVELHELP=1
, even whenTHREAD_CREATE_STACKTEST
is not set:Issues/PRs references