Date: Tue, 9 Mar 1999 12:00:23 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: =?iso-8859-1?Q?Rafael_Garc=EDa_Gonz=E1lez?= <rafael AT geninfor DOT com>
cc: djgpp AT delorie DOT com
Subject: RE: General Protection Failure
In-Reply-To: <006701be6991$dc4d9940$1800a8c0@falo>
Message-ID: <Pine.SUN.3.91.990309115945.7248H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 8 Mar 1999, =?iso-8859-1?Q?Rafael_Garc=EDa_Gonz=E1lez?= wrote:

> The program stops and I don't get de command prompt. If I try to write
> (symify), Windows tells this program is ended and I have to close it.
> 
> "Close on exit" check box is off
> 
> Other times, Windows close the process immediately with a short  text saying
> "General Protection Fault" in VMM...

Well, you will have to just find those bugs and fix them, then.
There's no way to change how Windows handles ill-behaved programs.

One way to find out where does the problem happen is to single-step
through the place where it crashes, until you see the crash.  Then at
least you'll know which line you need to debug.