Date:	13 Oct 92 09:34:32 GMT+1200
From:	chris moseley - MOZ <MOSELECW AT elec DOT canterbury DOT ac DOT nz>
Subject:	memory allocation and paging files
To:	djgpp AT sun DOT soe DOT clarkson DOT edu

 *  From: stefans AT bauv106 DOT bauv DOT unibw-muenchen DOT de (Stefan Schwarz)
 *  Subject: problems with memory allocation
 *
 *  The following simple program happily allocates memory until my
 *  machine dies. Although i should have no more than approx. 150
 *  MByte (disc + ram), it allocates more than 300 MB before
 *  hanging.

.            <DIR>    27-08-92  4:13p
..           <DIR>    27-08-92  4:13p
PG335FAA AAA  1134592 13-10-92  9:17a
         3 File(s)  55060480 bytes free

This is what I got from running Stefans program. (I had to undelete
the paging file). But the program claimed to have allocated 39.999 MB
of memory. Not bad for 8MB RAM plus a 1MB page file.

BUT - It quit on an exception 13 from the memory manager (QEMM),
which I think means the memory management got corrupted. My feeling
is that DJGPP has got its own memory management system outside of
whatever bounds it is allowed: in this case, quite probably it has a
page table or something that has filled the 5MB of extended memory
available.

moz

- Raw text -