pthread_attr_getguardsize(2)               pthread_attr_getguardsize(2)

  pthread_attr_getguardsize()

  NAME

    pthread_attr_getguardsize(), pthread_attr_setguardsize() - get or set the
    thread stack guard size attribute

  SYNOPSIS

    #include 

    int pthread_attr_getguardsize(const pthread_attr_t *attr, size_t
    *guardsize);
    int pthread_attr_setguardsize(pthread_attr_t *attr, size_t guardsize);

  IMLEMENTATION ISSUES IN THIS RELEASE

    This function is not implemented in this release. This will be corrected
    in a future release.

  DESCRIPTION

    The pthread_attr_setguardsize(2) function sets the stack guard size
    attribute in the thread attributes object referenced by attr using the
    value of the guardsize argument. The stack guard size attribute specifies
    the size in bytes of the guard area of the stack of the thread created
    using the attr thread attributes object. The guard area is additional
    memory allocated at the overflow end of the stack's area to prevent the
    stack's pointer from running off the stack into unallocated memory. An
    error results if the application overflows into the guard area.

    After the attributes have been set in the thread attributes object
    referenced by attr, the pthread_create(2) function can be called to create
    a new thread with the specified attributes. This function does not affect
    the current running thread.

    The pthread_attr_getguardsize(2) function retrieves the stack guard size
    attribute in the attr object, storing the value in the location referenced
    by the guardsize argument.

  RETURN VALUES

    On success, both functions return 0; otherwise, they return an error
    number.

  ERRORS

    Both functions can fail for the following reason:

    [EINVAL]
        The guardsize or attr parameter is invalid.

    Neither function returns [EINTR].

  SEE ALSO

    pthread_attr_destroy(2)

    pthread_attr_getstack(2)

    pthread_attr_getstackaddr()

    pthread_create(2)

  USAGE NOTES

    All of these functions are thread safe.

    None of these functions are async-signal safe.