Date: Thu, 23 Jul 1998 09:44:34 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Anton Helm <tony AT nt DOT tuwien DOT ac DOT at>
cc: djgpp AT delorie DOT com
Subject: Re: djgpp and WinNT 4.0 summary of problems
In-Reply-To: <3.0.5.32.19980722153436.0099e970@hal.nt.tuwien.ac.at>
Message-ID: <Pine.SUN.3.91.980723094413.14884B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Wed, 22 Jul 1998, Anton Helm wrote:

> I've been using djgpp v2.01 with WinNT 4.0 for a while
> and found some mysterious problems. None of them is really
> critical, but they are annoying and maybe someone knows
> how to deal with them.

Here are some more suggestions for investigating these problems.

  1) Do these problems happen with most/all DJGPP programs, or only
     with some?  For example, if you write a trivial 10-liner which
     just sits in an idle loop (in a way that is still interruptible
     by Ctrl-C), does it also behave this way?

     If not all programs misbehave like this, it would be interesting
     in particular to know whether the amount of memory used by the
     program is correlated with these problems.

  2) Try compiling the programs with Unixy sbrk algorithm, and see if
     that causes these problems to go away.

     The default sbrk sometimes uses techniques which NT disallows.
     Charles Sandmann once told me that he patched all his DJGPP
     images to use Unixy sbrk (it's a bit in the startup flags, and
     shouldn't be hard to find and change with a binary editor).

     To force a program to use Unixy sbrk, include the following in
     one of the source files and rebuild:

	#include <crt0.h>

	int _crt0_startup_flags = _CRT0_FLAG_UNIX_SBRK;