Date: Mon, 26 Feb 2001 08:41:39 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Michael Allison <michael DOT allison2 AT sympatico DOT ca>
cc: djgpp AT delorie DOT com
Subject: Re: Does Rhide work in WIN2000??
In-Reply-To: <Lhbm6.226388$Pm2.3669820@news20.bellglobal.com>
Message-ID: <Pine.SUN.3.91.1010226084111.21073A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 25 Feb 2001, Michael Allison wrote:

> Since so far it is only djgpp programs exhibiting the behaviour, there is
> some hesitation to do so.  Is anyone aware of any non-djgpp programs having
> the same problem?

What other widely used DPMI environment do we have?  The problem is
probably unique to DPMI programs.

> I also suspect that once the cause is fully understood, it will be
> possible to patch around it at the djgpp side, since you're unlikely
> to be able to patch ntvdm to work around djgpp)

If you look at the report produced by Dr Watson, you will clearly see
that it's NTVDM's own code which crashes, and it looks like it is
using the application's stack to do something when it crashes.  Using
an application's stack is an absolute no-no for system-level software,
because that stack might be invalid at any given moment.

Since NTVDM's source is not freely available to study, it is unlikely
that we will ever fully understand what happens.  We might have some
educated guess, given enough data and poking around, but that's about
all we can hope for.