Message-Id: <3.0.5.32.19971208220301.00cab100@modempool.com>
Date: Mon, 08 Dec 1997 22:03:01 -0500
To: "Joshua James Turpen" <44699 AT ef DOT gc DOT maricopa DOT edu>, djgpp AT delorie DOT com
From: bpmann AT modempool DOT com (Brian Mann)
Subject: Re:  Win95 DPMI and ___djgpp_hw_exception
In-Reply-To: <9712090224.AA26406@gcef.gc.maricopa.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

Hmmm. It crashes a 4dos session immediately on being run. It will run
forever in a dos box until you try to do something with another window.
This is on NT 4.0. As long as I leave the dos box as the focus, and don't
do anything else, it runs fine. 

Just thought you'd appreciate more info,
Brian


At 07:24 PM 12/8/97 -0700, Joshua James Turpen wrote:
>Ok, after being pointed out that my code doesn't lock the touched code and
>variables, here is a completely bulletproof program (as far as I can
>tell) that crashes under Win95 DPMI.  It may take a while, but it does
>crash.  I've had it crash anywhere from 1 minute to 15 minutes after
>starting it.  
>
>I would post a symified traceback, except it doesn't get there.  Windows
>intercepts the crash with the "This program has violated...." message and
>gives a pointer to 0028:c0002840, which is inside the VMM function
>Build_Int_Stack_Frame.
>
>
>This is a very scary bug.  If it does turn out to be a bug in Win95 DPMI,
>it's really going to hurt DJGPP, since the ___djgpp_hw_exception trick is
>the basis of signals under DJGPP.
>
>
>Josh Turpen 
>44699 AT ef DOT gc DOT maricopa DOT edu