Mail Archives: djgpp/1994/05/06/12:17:45
I have happily been doing dynamic memory allocation using
malloc,calloc and free.
With the advent of djgpp 1.11 I decided to check what is happening to
my memory using the _go32_dpmi_remaining_physical_memory() function.
Trying to run coreleft.c , attached to this file, seemed to indicate
some weird goings on e.g. showing an overhead of +/- 12K to allocate
and UCvector of 4096 bytes, not indicating that memory has been freed
etc.
This program has been tested with BorlandC++, using farcoreleft()
instead of _go32_dpmi_remaining_physical_memory() and the correct
headers of course.
Here it worked perfectly!
Is the problem with my code, with
_go32_dpmi_remaining_physical_memory() or with the malloc and free
commands in djgpp?
Thanks
----------------------------------------------------------------------
Nick van der Merwe
Department of Surveying and Geodetic Engineering
University of Cape Town |
South Africa | "Welcome to the Gnu South Africa"
Internet: neek AT cerecam DOT uct DOT ac DOT za
- Raw text -