Maps a file into memory. On UNIX, this is using the
TRUE, the mapped buffer may be modified, otherwise
it is an error to modify the mapped buffer. Modifications to the buffer
are not visible to other processes mapping the same file, and are not
written back to the file.
Note that modifications of the underlying file might affect the contents
GMappedFile. Therefore, mapping should only be used if the file
will not be modified, or if all modifications of the file are done
atomically (e.g. using g_file_set_contents()).
Available since: 2.32
The file descriptor of the file to load.
Whether the mapping should be writable.
The return location for a recoverable error.
The argument can be
If the return location is not
NULL, then you must initialize it to a
The argument will be left initialized to
NULLby the function if there are no errors.
In case of error, the argument will be set to a newly allocated
GError; the caller will take ownership of the data, and be responsible for freeing it.
A newly allocated
GMappedFile which must be unref’d
with g_mapped_file_unref(), or
NULL if the mapping failed.
|The caller of the function takes ownership of the data, and is responsible for freeing it.|