From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt) Description of problem: Setting a shell stack limit of 'unlimited' gives a (small) finite hardcoded stacksize from the pthread initialization, but setting a particular value that can be quite large honors the setting and gives you that value. This appears very counter-intuitive to users. Could 'unlimited' be set to mean really unlimited, or at least very very large. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: N/A Additional info:
Having stack limit set to unlimited is pretty common and this would mean no threads. 8MB is not that small (sufficient for most threaded apps) and you can have reasonable amount of threads created at the same time. If an application has special requirements (be it lots of threads with small stacks or just a few stack hungry threads), you can always setrlimit before first pthread_create call.
*** Bug 135741 has been marked as a duplicate of this bug. ***