Windows: fix error condition when File.open fails#13235
Merged
straight-shoota merged 1 commit intocrystal-lang:masterfrom Mar 28, 2023
Merged
Windows: fix error condition when File.open fails#13235straight-shoota merged 1 commit intocrystal-lang:masterfrom
File.open fails#13235straight-shoota merged 1 commit intocrystal-lang:masterfrom
Conversation
straight-shoota
approved these changes
Mar 27, 2023
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.
#13178 changed how files are opened on Windows, but it also inadvertently made it possible to create instances of
Filewith invalid descriptors. This makes things likeFile.read("foo"), wherefoois a non-existent file, crash withSTATUS_STACK_BUFFER_OVERRUN = 0xC0000409_u32. The exact failure is due to a Windows C runtime invalid parameter handler being invoked:In absence of a user-defined handler, the default action invokes
__fastfail, producing the above status code. It does not mean there is a stack overflow.The culprit is:
crystal/src/crystal/system/win32/file.cr
Lines 33 to 46 in 62f27b2
If the file is not found,
WinError.valueisERROR_FILE_NOT_FOUND, butErrnois untouched; thus the method returns{-1, Errno::NONE}, obscuring the error. This PR ensures allWinErrorvalues, not justERROR_FILE_EXISTS, are mapped toErrnovalues.