Re: glibc hppa build failure - ulimit
On Fri, May 13, 2005 at 05:38:33PM +0100, Matthew Wilcox wrote:
> On Fri, May 13, 2005 at 12:17:18PM -0400, Daniel Jacobowitz wrote:
> > 27319 mmap(NULL, 1073741824, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0 <unfinished ...>
> > 27319 <... mmap resumed> ) = -1 ENOMEM (Cannot allocate memory)
> >
> > Right now I don't think we could even rebuild glibc -21. The hppa
> > machines are configured with ulimit -s set to 1GB. This makes
> > LinuxThreads use 1GB thread stacks. Which is, um, pretty bad.
> >
> > Anyone know why this was done?
>
> PA machines grow the stack upwards, starting at 0xffffffff - hard
> stack limit. glibc never used to pay attention to the stack limit,
> choosing always to use 4MB stacks (iirc). When did glibc change that?
Probably when Carlos added a patch to glibc which defined
FLOATING_STACKS. Glibc throttles the size to 8MB if the rlimit is
infinity, but trusts the rlimit if it is explicitly larger than 8MB.
--
Daniel Jacobowitz
CodeSourcery, LLC
Reply to: