Unmap previously mapped addresses, exercising more control than possible with munmap()
#include <sys/mman.h> int munmap_flags( void * addr, size_t len, unsigned flags );
- The beginning of the range of addresses that you want to unmap.
- The length of the range of addresses, in bytes.
- 0, or a combination of the following bits:
For more information, see below.
Use the -l c option to qcc to link against this library. This library is usually included automatically.
The munmap_flags() function removes any mappings for pages in the address range starting at addr and continuing for len bytes, rounded up to the next multiple of the page size. Subsequent references to these pages cause a SIGSEGV signal to be set on the process.
If there are no mappings in the specified address range, then munmap_flags() has no effect.
If you specify 0 for the flags, munmap_flags() is the same as munmap(). The flags change the way munmap_flags() behaves, as follows:
- POSIX initialization of the page to all zeros is required the next time the underlying physical memory is allocated.
- Initialization of the underlying physical memory to zeros on its next allocation is optional. If you specify this flag, and you specify MAP_NOINIT when you next call mmap() for this physical memory, the POSIX requirement that the memory be zeroed is relaxed.
The memory-manager configuration (-m) option for procnto affects the default behavior of munmap_flags() (unless overridden by the flags argument), as detailed below:
- Act as if UNMAP_INIT_REQUIRED were specified (the default).
- Act as if UNMAP_INIT_OPTIONAL were specified.
- Failure; errno is set.
- The addresses in the specified range are outside the range allowed for the address space of a process.
- The function munmap_flags() isn't supported by this implementation.
Last modified: 2014-06-24