Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!cmcl2!yale!husc6!mit-eddie!genrad!decvax!ucbvax!TCGOULD.TN.CORNELL.EDU!garry
From: garry@TCGOULD.TN.CORNELL.EDU (Garry Wiegand)
Newsgroups: mod.computers.vax
Subject: Re: malloc, alloc, etc., and brk and sbrk
Message-ID: <8612221720.AA17850@tcgould.tn.cornell.edu>
Date: Mon, 22-Dec-86 12:20:14 EST
Article-I.D.: tcgould.8612221720.AA17850
Posted: Mon Dec 22 12:20:14 1986
Date-Received: Tue, 23-Dec-86 21:45:13 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Cornell Engineering && Flying Moose Graphics
Lines: 10
Approved: info-vax@sri-kl.arpa

Try malloc'ing and then freeing a bunch of memory at the top of the program,
sufficient to take care of any random getenv(), open(), etc calls that
may come up during the life of the program.

Or fix emacs not to assume that it has complete 100% control over sbrk()-style
memory allocating. That's dangerous even on a Unix system. Sbrk() and malloc()
can always be mixed freely; the danger is in assuming that different calls to
sbrk will return consecutive memory locations.

garry wiegand   (garry%cadif-oak@cu-arpa.cs.cornell.edu)