#include <pthread.h> int pthread_attr_getstack(const pthread_attr_t *restrict attr, void **restrict stackaddr, size_t *restrict stacksize); int pthread_attr_setstack(pthread_attr_t *attr, void *stackaddr, size_t stacksize);
The stack attributes specify the area of storage to be used for the created thread's stack. The base (lowest addressable byte) of the storage shall be stackaddr, and the size of the storage shall be stacksize bytes. The stacksize shall be at least {PTHREAD_STACK_MIN}. The pthread_attr_setstack() function may fail with [EINVAL] if stackaddr does not meet implementation-defined alignment requirements. All pages within the stack described by stackaddr and stacksize shall be both readable and writable by the thread.
If the pthread_attr_getstack() function is called before the stackaddr attribute has been set, the behavior is unspecified.
The behavior is undefined if the value specified by the attr argument to pthread_attr_getstack() or pthread_attr_setstack() does not refer to an initialized thread attributes object.
The pthread_attr_getstack() function shall store the stack attribute values in stackaddr and stacksize if successful.
The pthread_attr_setstack() function shall fail if:
The pthread_attr_setstack() function may fail if:
These functions shall not return an error code of [EINTR].
The following sections are informative.
While it might seem that an application could detect stack overflow by providing a protected page outside the specified stack region, this cannot be done portably. Implementations are free to place the thread's initial stack pointer anywhere within the specified region to accommodate the machine's stack pointer behavior and allocation requirements. Furthermore, on some architectures, such as the IA-64, ``overflow'' might mean that two separate stack pointers allocated within the region will overlap somewhere in the middle of the region.
After a successful call to pthread_attr_setstack(), the storage area specified by the stackaddr parameter is under the control of the implementation, as described in Section 2.9.8, Use of Application-Managed Thread Stacks.
The specification of the stackaddr attribute presents several ambiguities that make portable use of these functions impossible. For example, the standard allows implementations to impose arbitrary alignment requirements on stackaddr. Applications cannot assume that a buffer obtained from malloc() is suitably aligned. Note that although the stacksize value passed to pthread_attr_setstack() must satisfy alignment requirements, the same is not true for pthread_attr_setstacksize() where the implementation must increase the specified size if necessary to achieve the proper alignment.
The Base Definitions volume of POSIX.1-2017, <limits.h>, <pthread.h>
Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .