Fix fread segfault with \x1a bytes #7415
Open
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
Reproduces issue Rdatatable#7407 where fread crashes when reading files with \x1a (ASCII SUB) character. Manual testing confirms both test cases trigger segmentation fault as expected.
|
Please confirm you've read CONTRIBUTING |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What I Added
Two test cases that show the bug exists:
Both tests crash right now (expected).
What Comes Next
Next commit will fix the actual bug in src/fread.c by handling \x1a as a field terminator.
Screenshots
See attachment: Screenshot showing the segfault crash message
Fixes #7407