Xref: news2.mv.net comp.os.msdos.djgpp:1052 From: Charles Sandmann Newsgroups: comp.os.msdos.djgpp Subject: Re: CWSDPMI bug [was Infernal compiler error.] Date: Mon, 12 Feb 1996 21:28:52 CST Organization: Rice University, Houston, Texas Lines: 21 Message-ID: <31200574.sandmann@clio.rice.edu> References: <271AEA71A95 AT fs2 DOT mt DOT umist DOT ac DOT uk> Reply-To: sandmann AT clio DOT rice DOT edu NNTP-Posting-Host: clio.rice.edu To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp > > Maybe. The current distributed CWSDPMI can run up to around 200 memory zones > > before returning 0 for the malloc() call.... > What is CWSDPMI as distinct from other versions of DPMI? It's a DPMI I wrote which was originally based on GO32's code. It went through 9 betas and noone saw this problem in the last two months. Its easily corrected by getting ftp.neosoft.com:pub/user/s/sandmann/csdpmi1heapfix.zip > When will there be a version of djgpp with this bug corrected? It's not a djgpp bug, it's a CWSDPMI bug. And the fix was announced before, and above again. There are a couple of things I need to to in the ring 0 version before the next release, and I'll include this stuff when I get the time to finish the ring 0 stuff. The only time this would be seen is if you are running a program which allocates more than 11 Mb of memory in pieces of less than 64K bytes. Only a very large C++ compile (or a program of your own design) is likely to do this. If a program has a need to do this, grab the fix, else don't worry about it. Or use Windows, or 386max, or QDPMI, or OS/2. Lots of options.