[GHC] #8604: Some stack/vmem limits (ulimit) combinations causing GHC to fail

[GHC]

#8604: Some stack/vmem limits (ulimit) combinations causing GHC to fail
-------------------------------------+-------------------------------------
        Reporter:  clavin            |                   Owner:
            Type:  bug               |                  Status:  new
        Priority:  normal            |               Milestone:
       Component:  Documentation     |                 Version:  7.6.3
      Resolution:                    |                Keywords:
Operating System:  Other             |            Architecture:  x86_64
 Type of failure:  Documentation     |  (amd64)
  bug                                |               Test Case:
      Blocked By:                    |                Blocking:
 Related Tickets:                    |  Differential Revisions:
-------------------------------------+-------------------------------------

Comment (by rwbarton):

 I'm wary of trying to document the underlying behavior of the operating
 system in the user's guide, especially when that behavior is likely to
 vary between different operating systems. It seems that the behavior of
 ghc (or any program built with the threaded runtime) is no different than
 any other program that starts multiple OS threads. Granted it might not be
 obvious to the user that ghc itself starts multiple threads, but then they
 will never know where to look in the documentation to learn this.

 But I guess we could at least clarify in the documentation for some or all
 of the `-K/-k*` options that they refer to the Haskell stack, not the C
 stack.

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8604#comment:7>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler