Function open [src]

In WASI, this error may occur when the file descriptor does not hold the required rights to open a new resource relative to it.

Path contains characters that are disallowed by the underlying filesystem.

One of these three things:

• pathname refers to an executable image which is currently being executed and write access was requested.
• pathname refers to a file that is currently in use as a swap file, and the O_TRUNC flag was specified.
• pathname refers to a file that is currently being read by the kernel (e.g., for module/firmware loading), and write access was requested.

The underlying filesystem does not support file locks

Either:

• One of the path components does not exist.
• Cwd was used, but cwd has been deleted.
• The path associated with the open directory handle has been deleted.
• On macOS, multiple processes or threads raced to create the same file with O.EXCL set to false.

The file is too large to be opened. This error is unreachable for 64-bit targets, as well as when opening directories.

WASI-only; file paths must be valid UTF-8.

Windows-only; file paths provided by the user must be valid WTF-8. https://simonsapin.github.io/wtf-8/

The path refers to directory but the DIRECTORY flag was not provided.

Using FIXED_NOREPLACE flag and the process has already mapped memory at the given address

The underlying filesystem of the specified file does not support memory mapping.

The path exceeded max_path_bytes bytes.

On Windows, \\server or \\server\share was not found.

A new path cannot be created because the device has no room for the new file. This error is only reachable when the CREAT flag is provided.

A component used as a directory in the path was not, in fact, a directory, or DIRECTORY was specified and the path was not a directory.

The path already exists and the CREAT and EXCL flags were provided.

The prot argument asks for PROT_EXEC but the mapped area belongs to a file on a filesystem that was mounted no-exec.

Insufficient kernel memory was available, or the named file is a FIFO and per-user hard limit on memory allocation for pipes has been reached.

The Operating System returned an undocumented error code.

This error is in theory not possible, but it would be better to handle this error than to invoke undefined behavior.

When this error code is observed, it usually means the Zig Standard Library needs a small patch to add the error code to the error set for the respective function.