[RESEND] [PATCH] fix allocation of NPTL thread stack guard area
Chris Demetriou
cgd@google.com
Fri May 30 15:00:00 GMT 2008
On Thu, May 29, 2008 at 08:50, Josh Boyer <jwboyer@gmail.com> wrote:
> If I remember correctly, this issue has been brought up before. The
> answer that was given previously was that POSIX is slightly ambiguous
> here and glibc is correct in it's current behavior.
Looking at the Austin Group mailing list archives, specifically
http://www.opengroup.org/austin/interps/show_mail.tpl?CALLER=show_archive.tpl&source=L&listname=austin-group-l&id=8778
it looks like there was a discussion about the meaning of PTHREAD_STACK_MIN.
However, I haven't found anything there or in the various libc list
archives about whether or not (in essence) the stack size allocated
when both pthread_attr_setstacksize + pthread_attr_setguardsize is
supposed to be "stack size" or "stack size + guard size".
As I noted, LinuxThreads did the latter, and (IMO) the standard is clear enough.
If people really think the standard is ambiguous, I could probably
raise the question elsewhere to try to get clarification.
chris
More information about the Libc-alpha
mailing list