Date:	Thu, 21 Jun 2001 13:13:44 +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:	<3b31a342.174762361@news.primus.ca>
Message-ID:	<Pine.SUN.3.91.1010621130805.9042B-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 Thu, 21 Jun 2001, Graaagh the Mighty wrote:

> On Tue, 19 Jun 2001 12:32:03 +0300 (IDT), Eli Zaretskii
> <eliz AT is DOT elta DOT co DOT il> sat on a tribble, which squeaked:
> 
> >It would be much better to post the crash message here, instead of 
> >describing it.
> 
> Saved this one for just such an occasion.
> 
> General Protection Fault at eip=123a; flags=3246
> eax=ffffc286 ebx=0000100a ecx=00000015 edx=000b0000 esi=00000000 edi=ffffc286
> ebp=6d200912 esp=00000758 cs=e7 ds=cf es=ef fs=cf gs=0 ss=cf error=0000

This comes from CWSDPMI, see section 12.2 of the FAQ.  That's why you 
don't see a traceback.

As I said earlier, I'd first suspect some stack smashage, like a huge 
automatic variable or extremely deep recursion.

> Looks like it died in ring-0 code, which it shouldn't have, since
> cwsdpmi and all of the device drivers are presumably bug-free...

You misunderstand what happens: the exception (GPF) indeed happens inside 
CWSDPMI, but the reason is outside CWSDPMI.  So CWSDPMI bugs are not 
relevant here; _your_ bugs are.

- Raw text -