Date:	Sun, 24 Jun 2001 10:55:32 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp AT delorie DOT com
Subject:	Re: Peculiar behavior of program.
In-Reply-To:	<3b351a50.104687584@news.primus.ca>
Message-ID:	<Pine.SUN.3.91.1010624105431.13700I-100000@is>
MIME-Version:	1.0
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

On Sat, 23 Jun 2001, Graaagh the Mighty wrote:

> >No, I blame it on you: it's your bug that caused a GPF inside CWSDPMI.
> 
> There are clearly two bugs here:
> 1. My code crashed. Ergo, it has a bug.

Yes.

> 2. CWSDPMI code crashed. Ergo, it has a bug.

No, CWSDPMI didn't crash.  Where do you think that message with
registers come from?  CWSDPMI detected the GPF, printed the message,
aborted the program, then exited.

In other words, the crash message comes from CWSDPMI, but CWSDPMI
didn't crash.

> If the second bug didn't exist, it might be a tad easier for me to
> debug the first...

When GPF's happen inside CWSDPMI, it usually means that the
application's memory or exception table is so badly scrogged that it
doesn't make sense to let the application code run.  It can simply be
dangerous: a bad selector or exception table can wipe your disk clean
(it happened in the past).  So CWSDPMI plays it safe and aborts the
program before it could do any more harm.

- Raw text -