Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83 (MC830919); site kvvax4.UUCP
Path: utzoo!watmath!clyde!akgua!mcnc!decvax!mcvax!kvport!kvvax4!esa
From: esa@kvvax4.UUCP (Esa K Viitala)
Newsgroups: net.unix-wizards,net.micro.pc
Subject: Re: Csh bug?  (Grows forever)
Message-ID: <396@kvvax4.UUCP>
Date: Thu, 10-May-84 10:17:58 EDT
Article-I.D.: kvvax4.396
Posted: Thu May 10 10:17:58 1984
Date-Received: Sun, 13-May-84 09:52:10 EDT
References: <253@vaxine.UUCP> <258@intelca.UUCP>
Organization: Kongsberg Vaapenfabrikk, CTG, P.O Box 25, N-3601 Kongsberg, Norway
Lines: 21


>>We have recently purchased a number of Venix's and noticed that their csh
>>seems to grow ad nauseum, eventually blowing out its (small/medium model) data
>>segment.  Thought this was just a bad port on Venturcom's part......

>The same thing seems to happen under xenix's csh, I have no reason why,
>but when it runs out of space, it is not handled very gracefully....
>(i.e., core dump time)

Here too, I think. We have 4.1bsd/vax11/780, and occasionally
csh says 'assertion botched <something or other>' and then nothing.
This comes from a memory allocation routine, I forgot the name, if
either the chain of blocks has corrupted or the the chain is empty.
I've concluded that it ain't corrupted.

Fixes anybody?
-- 

   Esa K Viitala  {decvax,philabs}!mcvax!kvport!kvvax4!esa
   A/S Kongsberg Vaapenfabrikk,CTG4,P.O.Box 25,N-3601 Kongsberg,Norway
   tel. 473-739644   tlx. 71491 vaapn n