Mail Archives: djgpp/2004/03/20/18:30:38
Brian Inglis wrote:
> kantsel AT mail DOT ru (Anthony) wrote:
> >DJ Delorie <dj AT delorie DOT com> wrote in message news:
>
>>> > 1. What memory should I monitor (DOS (below 1MB), upper,...)
>>>
>>> Virtual.
>>>
>>> > 2. How can do that?
>>>
>>> You don't want to monitor free memory, you want to monitor *used*
>>> memory (other things on the computer might use memory too). Most
>>> programs can use the sbrk(0) call to ask libc where the top of your
>>> memory is. If it doesn't change, you're not asking for more memory.
>>>
>>> The exception is if you choose the "non-moving sbrk" option (nearptr,
>>> DMA, etc need this) in which case your memory range is discontiguous
>>> and sbrk() moves all over the place during allocation. But at least
>>> you can tell if it changes *at all*.
>>
>> Thanks, I'll use it. But sill, if I want to know how much memory do I
>> have left, how can I?
>
> There's a bunch of new functions giving malloc information, esp.
> mallinfo, malloc_debug, mallocmap, in the DJGPP 2.04 beta release, if
> you want to go to the effort of installing and trying a beta release.
Those are all available in 2.03 with the nmalloc package I
mentioned earlier. Just follow the instructions to link the
malloc and malldbg objects before the library search. What is NOT
available in that package is a memalign routine that works for
arbitrary alignment.
--
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net> USE worldnet address!
- Raw text -