> > in case that a process failed in getting resource such as memory or > > process, > > what it should do is very limited: puts out some message and exits. > > this is right behavior. > > practically, for most simple programs fork error is handled by sysfatal(). > but things get more tricky for libthread programs like rio.
i'd forgotten the added difficulty with the 32-bit kernels that plan 9 overcommits memory. so in a low-memory situation, a process can be killed by using more stack! - erik
