Date: Thu, 10 May 2001 10:12:58 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: ywshei <ywshei AT tao DOT iam DOT ntu DOT edu DOT tw>
cc: djgpp AT delorie DOT com
Subject: Re: GPF after a litte bit of running time.
In-Reply-To: <9dcker$9ea$1@gemini.ntu.edu.tw>
Message-ID: <Pine.SUN.3.91.1010510101241.3009E-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 Thu, 10 May 2001, ywshei wrote:

> My program is running under DOS 7.0 (without win98 GUI).
> There are five ISRs(COM1/0x3f8/IRQ4, COM2/0x2f8/IRQ3, COM3/0x3e8/IRQ5,
> 8255DIO/0xa00/IRQ7, PCI9111 A/D, D/A, DIO card) working in the same time. It
> is hardware dependent.

In that case, it's almost certain that the problem is the failure to
lock some code or data which are touched by a hardware interrupt
handler.

The FAQ describes the `_CRT0_FLAG_LOCK_MEMORY' bit in the DJGPP
startup flags variable which will cause all memory of your program to
be locked automatically.  I suggest to try that and see if it solves
the problem.  (If your program is small enough to fit into the
available physical RAM, and if it never needs to run on memory-starved
machines, you can simply leave the `_CRT0_FLAG_LOCK_MEMORY' bit set.)