This is the mail archive of the
mailing list for the glibc project.
[Bug libc/11787] Program with large TLS segment fails aio_write
- From: "carlos_odonell at mentor dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Mon, 26 Mar 2012 14:28:05 +0000
- Subject: [Bug libc/11787] Program with large TLS segment fails aio_write
- Auto-submitted: auto-generated
- References: <firstname.lastname@example.org/bugzilla/>
--- Comment #22 from Carlos O'Donell <carlos_odonell at mentor dot com> 2012-03-26 14:28:05 UTC ---
(In reply to comment #21)
> I think it will least surprise users if "stack" means the stack actually
> available to the thread, not including implementation details such as TLS,
> so they can work with tools that determine the amount of stack space used
> by individual functions to work out how large a stack may be needed.
That sounds like a reasonable position to take. Do we know if other OSs
interpret POSIX `stack' in this way?
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.