Date:	Thu, 12 Feb 1998 22:40:18 -0800 (PST)
Message-Id:	<199802130640.WAA14529@adit.ap.net>
Mime-Version:	1.0
To:	daydream AT cs DOT tu-berlin DOT de, djgpp AT delorie DOT com
From:	Nate Eldredge <eldredge AT ap DOT net>
Subject:	Re: malloc - free

At 07:08  2/12/1998 +0100, Christian Fleischer wrote:
>Hello!
>
>My problem goes as follows:
>I have quite complex dynamic data-structures and want to control if they
>are removed correctly from memory when I quit my program.
>What function can I use to check how many memory is still available to
>check if itīs the same as when the program starts?
>I tried it with something like _go32_remaining_virtual_memory and
>..physical.. but it didnīt produce the expected results. When I wanted
>to allocate 90000 bytes the remaining memory was reduced by 3*65536. I
>can figure out, that maybe go32 allocates in 65536 chunks, but where do
>I get the EXACT value?
>
>Is there a simple answer or a faq about it?
FAQ section 16.2 should explain most of it.
>Where is the difference between _go32..., _djgpp... and _dpmi... ? Some
>functions seem to produce the same results? Which should one prefer? Or
>is there always a small difference between similar results?
In general, the `__dpmi' group of functions are direct connections to the
standard DPMI services. The `_go32' functions are similar, but sometimes
have extra functionality. They mostly exist for backward compatibility to
DJGPP v1. See also FAQ section 18.10. The `__djgpp' functions, where they
exist, normally provide more convenient interfacing.

Nate Eldredge
eldredge AT ap DOT net

- Raw text -