Re: glibc hppa build failure - ulimit
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?
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
Reply to: