🚀 go-pugleaf

On version 1.04 of the djgpp port of gcc, I have run a small program which
continually allocates memory with malloc, until it returns a null pointer.
However, it never seems to to this.  For example, malloc (50*1024*1024)
returns a non-null pointer.  What happens in the first situation, is that
DOS returns a segmentation error and bombs the program.  Furthermore,
the 9+ MB of extended memory which was available prior to running the
program is not available after, as determined by a memory checking program.
The memory manager is himem.sys.

Any thoughts/ideas about this?

BTW running the same program with turbo c, yields a maximum available memory
of about 500K (give or take), since it doesn't handle extended memory directly.

Thanks

Allen Gordon



--
Allen Gordon 
University of Colorado, Boulder
gordon@tramp.colorado.edu 
gordon_A@cubldr.colorado.edu