🚀 go-pugleaf

Allen Gordon (gordon@news.colorado.edu) writes:

>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?

Doesn't the DOS extender give you up to 512 MB (256 MB RAM and 256 MB
disk) of virtual memory?  If so (or in the ballpark for numbers),
it sounds like a conflict with the extender and your DOS.

As for the missing memory, my understanding of the extended memory capability
says that applications must return memory (DOS doesn't handle it) or
no one else will get it.

I'm afraid I don't have more information on this - I've installed
djgpp and run the two sample programs and that's about it.

Pete