Repository navigation
Refactor Crystal::System.retry_with_buffer calling #to_slice - #14614
Merged
straight-shoota merged 2 commits intoJun 11, 2024
Merged
straight-shoota merged 2 commits into
straight-shoota merged 2 commits into
Conversation
Contributor
The relevant change is probably that before this commit, the whole crystal/src/crystal/system/unix.cr Line 5 in f0bd16a After this, It seems like there always has been a stack corruption, but only inside the irrelevant padding region. |
straight-shoota
marked this pull request as ready for review
May 29, 2024 13:40
ysbaddaden
approved these changes
Jun 10, 2024
1 task done
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
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.
This is a trivial refactor, moving the call to
StaticArray#to_sliceout of the loop. On repeat iterationsbufis aSliceso#to_sliceis actually a no-op.However, this change breaks some specs in the interpreter where it produces only gibberish. Looks like stack corruption.
I don't think this change is responsible, it just makes the problem visible.
Related to #14613
Depends on #14615