Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ncar!hao.ucar.edu!cmiller
From: cmiller@hao.ucar.edu (Charlie Miller)
Newsgroups: comp.realtime
Subject: vxWorks memory partitions
Message-ID: <3213@ncar.ucar.edu>
Date: 10 May 89 22:42:51 GMT
Sender: news@ncar.ucar.edu
Reply-To: cmiller@hao.ucar.edu (Charlie Miller)
Organization: High Altitude Observatory/NCAR, Boulder CO
Lines: 16


The apparent problem: In the debug cycle of modify, load, try, modify, reload,
vxWorks eventually uses up all available memory by not deallocating partitions
allocated to each program loaded even though the new program has the same
name.  It just allocates new partitions until no more are available then
refuses to allow loads.  The only way I have found to get around this is
to manually do free(program_name) from the shell or to reset. There must be
a way to automate this process.

Any suggestions??

Also, I would like to hear from other vxWorks users out there.  What are
your applications, etc.

Charlie Miller
cmiller@hao.ucar.edu