Test segfault #216
Merged
Test segfault #216
Conversation
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
ioquatix
force-pushed
the
test-segfault
branch
3 times, most recently
from
19e4dac to
4c2b650
Compare
See <ruby/ruby#7460> for more details.
ioquatix
added a commit
that referenced
this pull request
Mar 7, 2023
…`. (#216) See <ruby/ruby#7460> for more details.
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.
There is a race condition which can cause a segfault/
rb_bugin very rare cases. It is hard to reproduce. I added a repro script that only works on Linux, and only once in every 3-4 runs, only when usingio_uring. I'll think about whether I can add a specific test case.Types of Changes
Contribution