Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!mcnc!rutgers!iuvax!pur-ee!uiucdcs!uxc.cso.uiuc.edu!uicsgva!steven
From: steven@uicsgva.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: MSC _memavl()
Message-ID: <4600006@uicsgva>
Date: 18 Jan 88 16:45:00 GMT
Lines: 15
Nf-ID: #N:uicsgva:4600006:000:638
Nf-From: uicsgva.UUCP!steven    Jan 18 10:45:00 1988


In MSC 5.0, small model, I'm using _memavl() to determine the amount of avail.
I use up to 80% of that space to do some reading/writing.  This works fine
the first time I try it (when reading data).  I then free() this space.
Later in the program, when writing, I repeat the same process to write.
_memavl() returns a reasonable result, but when I try to do a subsequent
malloc, it fails.  The documentation seems to lead you into believing that
you can malloc anything that _memavl() returns.

Any ideas?  I've run the heap check routines, and they don't see any
problems.

steven@polaris.csg.uiuc.edu
or
steven%polaris@uxc.cso.uiuc.edu