Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site fortune.UUCP
Path: utzoo!watmath!clyde!burl!we13!ihnp4!fortune!olson
From: olson@fortune.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Csh bug?  (Grows forever) - (nf)
Message-ID: <3255@fortune.UUCP>
Date: Mon, 7-May-84 23:05:45 EDT
Article-I.D.: fortune.3255
Posted: Mon May  7 23:05:45 1984
Date-Received: Tue, 8-May-84 07:23:19 EDT
Sender: notes@fortune.UUCP
Organization: Fortune Systems, Redwood City, CA
Lines: 22

#R:vaxine:-25300:fortune:11600094:000:760
fortune!olson    May  7 18:25:00 1984

The csh (at least the 4.1 csh) does use malloc and free to do memory
allocation.  (In fact, it does more malloc'ing and free'ing than any
other program I've seen!)

It is possible that during the port someone messed up
on signal handling, so that things are left in a strange state after
an interrupt.  It is also possible that some kind of error was
introduced to the malloc/free/realloc code that only shows up under
intensive use.

If the person(s) doing the port made modifications to the csh, they
could have introduced some errors; malloc/free are very unforgiving
of errors (particularly those involving freeing memory not allocated
by malloc).

	Dave Olson, Fortune Systems
	UUCP: {ihnp4,ucbvax!amd70}!fortune!olson
	ARPA: amd70!fortune!olson@BERKELEY