Xref: news2.mv.net comp.os.msdos.djgpp:5561
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: page fault
Date: Sun, 30 Jun 1996 15:18:08 CDT
Organization: Rice University, Houston, Texas
Lines: 11
Message-ID: <31d6e100.sandmann@clio.rice.edu>
References: <Pine DOT GSO DOT 3 DOT 94 DOT 960629234709 DOT 9795E-100000 AT zippy>
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

> I would just like to support what is being said here.
> I can crash cwsdpmi (i think thats what is crashing) merely by running a 
> program which uses it, and pausing and unpausing a bunch of times...

I haven't heard about this, I haven't seen this, and don't have an example
or someone who can reproduce it.  Things don't get fixed unless they are 
reported and reproducible.  The example cited before looked like a program
bug in locking a hardware interrupt handler.  When you "pause" you spend
all of your time in real mode, so a reflected HW interrupt is much more
likely than one that stays in PM.  Since only RM reflected interrupts will
turf up improperly locked memory, you might need to pause to find them.