diff options
| author | Jonathan Marler <johnnymarler@gmail.com> | 2024-03-13 18:39:20 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-03-13 21:39:20 -0400 |
| commit | 32f602ad167e90825ef1f980046a7611cfcfb5fe (patch) | |
| tree | 82f2eac428620e992caba8031953561b4f8e25a8 /src/Compilation/Config.zig | |
| parent | 2008b14bc76b54f29b07e8570a094c17aefea9d5 (diff) | |
| download | zig-32f602ad167e90825ef1f980046a7611cfcfb5fe.tar.gz zig-32f602ad167e90825ef1f980046a7611cfcfb5fe.zip | |
std.os.windows: handle OBJECT_NAME_INVALID in OpenFile (#19288)
It's been seen on Windows 11 (22H2) Build 22621.3155 that NtCreateFile
will return the OBJECT_NAME_INVALID error code with certain path names.
The path name we saw this with started with `C:Users` (rather than
`C:\Users`) and also contained a `$` character. This PR updates our
OpenFile wrapper to propagate this error code as `error.BadPathName`
instead of making it `unreachable`.
see https://github.com/marler8997/zigup/issues/114#issuecomment-1994420791
Diffstat (limited to 'src/Compilation/Config.zig')
0 files changed, 0 insertions, 0 deletions