Enabling TLS detects stack overflow in a few tests #53687
Merged
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.
Because TLS stores critical thread information at the top of each stack, overflows in subsequent stacks will write over that and cause general chaos. This means that enabling thread local storage will cause some tests to fail simply because they overflow their stacks in a way which was not detected without TLS enabled.
These three patches increase stack sizes in tests (probably by way more than necessary) to make them work when thread local storage is enabled.