shmat - shared memory attach operation
#include <sys/shm.h> void *shmat(int shmid, const void *shmaddr, int shmflg);
The shmat() function attaches the shared memory segment associated with the shared memory identifier specified by shmid to the address space of the calling process. The segment is attached at the address specified by one of the following criteria:
- If shmaddr is a null pointer, the segment is attached at the first available address as selected by the system.
- If shmaddr is not a null pointer and (shmflg&SHM_RND) is non-zero, the segment is attached at the address given by (shmaddr-((uintptr_t)shmaddr%SHMLBA)) The character % is the C-language remainder operator.
- If shmaddr is not a null pointer and (shmflg&SHM_RND) is 0, the segment is attached at the address given by shmaddr.
- The segment is attached for reading if (shmflg&SHM_RDONLY) is non-zero and the calling process has read permission; otherwise, if it is 0 and the calling process has read and write permission, the segment is attached for reading and writing.
Upon successful completion, shmat() increments the value of shm_nattch in the data structure associated with the shared memory ID of the attached shared memory segment and returns the segment's start address.
Otherwise, the shared memory segment is not attached, shmat() returns -1 and errno is set to indicate the error.
The shmat() function will fail if:
- Operation permission is denied to the calling process, see IPC.
- The value of shmid is not a valid shared memory identifier; the shmaddr is not a null pointer and the value of (shmaddr-((ptrdiff_t)shmaddr%SHMLBA)) is an illegal address for attaching shared memory; or the shmaddr is not a null pointer, (shmflg&SHM_RND) is 0 and the value of shmaddr is an illegal address for attaching shared memory.
- The number of shared memory segments attached to the calling process would exceed the system-imposed limit.
- The available data space is not large enough to accommodate the shared memory segment.
The POSIX Realtime Extension defines alternative interfaces for interprocess communication. Application developers who need to use IPC should design their applications so that modules using the IPC routines described in IPC can be easily modified to use the alternative interfaces.
exec, exit(), fork(), shmctl(), shmdt(), shmget(), shm_open(), shm_unlink(), <sys/shm.h>, IPC.
Derived from Issue 2 of the SVID.