Message-ID: <253@vaxine.UUCP>
Date: Thu, 3-May-84 08:14:31 EDT
Article-I.D.: vaxine.253
Posted: Thu May  3 08:14:31 1984
Date-Received: Sat, 5-May-84 07:30:00 EDT
Organization: Automatix Inc., Billerica, MA
Lines: 15

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, but seem to
see the same effect on our Vaxen (of course the data segment there has yet
to blow out...).  Has anyone else noticed this bug/feature?  No we don't have
our history set to infinity.

Additional detail:  it almost looks like csh is just never freeing anything.
One quick way to blow out our Venix is to source a .cshrc full of aliases
a couple of times in a row.  I do recall that csh does some funny mumbo-jumbo
in place of malloc/free...

                                o.o     -ptw
                                 ~

Message-ID: <483@dual.UUCP>
Date: Mon, 7-May-84 10:20:20 EDT
Article-I.D.: dual.483
Posted: Mon May  7 10:20:20 1984
Date-Received: Tue, 8-May-84 07:16:23 EDT
References: <253@vaxine.UUCP> <258@intelca.UUCP>
Organization: Dual Systems, Berkeley, CA
Lines: 4

Our copy of CSH has never seemed to show this behavior - perhaps somebody
over at UniSoft might enlighten us as to the nature of the problem, since
they seem to have fixed it. On the other hand, maybe not - they may have
a competitive advantage here. How `bout it, guys?

Message-ID: <258@intelca.UUCP>
Date: Sun, 13-May-84 02:16:25 EDT
Article-I.D.: intelca.258
Posted: Sun May 13 02:16:25 1984
Date-Received: Wed, 9-May-84 03:29:26 EDT
References: <253@vaxine.UUCP>
Organization: Intel, Santa Clara, Ca.
Lines: 10
Xref: 1116 341

 > 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)
-- 
Ken Shoemaker, Intel, Santa Clara, Ca.
{pur-ee,hplabs,ucbvax!amd70,ogcvax!omsvax}!intelca!kds

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 ' 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