From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: memmory-problems with djgpp and cwsdpmi
Date:	22 Oct 2002 16:49:06 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	22
Message-ID:	<ap3vi2$s7f$1@nets3.rz.RWTH-Aachen.DE>
References:	<3DB57E77 DOT 57D69156 AT cityweb DOT de>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 1035305346 28911 137.226.32.75 (22 Oct 2002 16:49:06 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	22 Oct 2002 16:49:06 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Marcus Koch <mw DOT koch AT cityweb DOT de> wrote:

> 1.) As you see it only consumes 8192 bytes of memmory but i requested
> 1000000.

No, that's not what you really see.  It's only what you think you see.

DJGPP, like the vast majority of Unix systems these days, is a "late
commit" allocator, i.e. it won't allocate any memory from the pool
(i.e. the DPMI server) until you actually touch it.  To get a more
useful answer, try calloc() instead of malloc().

> Furthermore as i tried out djgpp a few month ago i had to load
> cwsdpmi in oder to compile or run programs. But now programs run and
> compile without loading cwsdpmi !!

The latter is the normal intended behaviour.  You probably didn't have
CWSDPMI.EXE anywhere in your PATH before, or anywhere else where
DJGPP-built programs would have found it automatically.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -