Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!bellcore!faline!ulysses!gatech!mcnc!seismo!vrdxhq!vsedev!ron
From: ron@vsedev.UUCP
Newsgroups: comp.bugs.sys5
Subject: Re: Sys V handling of insufficient swap space.
Message-ID: <444@vsedev.VSE.COM>
Date: Wed, 4-Mar-87 09:57:58 EST
Article-I.D.: vsedev.444
Posted: Wed Mar  4 09:57:58 1987
Date-Received: Fri, 6-Mar-87 22:37:55 EST
References: <1035@wang7.UUCP> <1078@hoxna.UUCP>
Reply-To: ron@vsedev.VSE.COM (Ron Flax)
Organization: VSE Software Development Lab
Lines: 24
Keywords: swap crash

In article <1078@hoxna.UUCP> lou@hoxna.UUCP ( L. Marco ) writes:
>
>> < Sys5 doesn't handle running out of swap space well.  A program
>> that supposedly demonstrates this is provided >
>
>	First of all, your program won't run on many systems,
>hoxna included, because that huge auto array you allocate won't fit
>on the stack.  (We're not *all* running Amdahls, y'know).
>

Well after trying to compile the er um crash program on my Sys V.2
Altos 3068, I realized that I needed to move the large array
declaration out of local space and into global space, then it compiled
fine.

But the Altos eligantly handled the situation by returning a kernel
generated error message indicating that the system was incapable of
supporting the memory allocation request. So it turns out that at least
this system protects itself from this type of devistation.

--
ron@vsedev.VSE.COM	(Ron Flax)
UUCP:	..!seismo!vsedev!ron
INET:	vsedev.VSE.COM!ron@seismo.CSS.GOV