From:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Windows NT
Date:	25 May 1997 18:55:30 GMT
Organization:	The National Capital FreeNet
Message-ID:	<5ma1v2$avb@freenet-news.carleton.ca>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 970525140343 DOT 4960X-100000 AT is>
Reply-To:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
NNTP-Posting-Host:	freenet5.carleton.ca
Lines:	29
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) writes:
> On 24 May 1997, Larry Ellis wrote:
> 
>> Under Windows NT 4.0, DJGPP executables often generate SIGSEV failures
>> if CONTROL-BREAK is used.  After the segment violation occurs, the DOS
>> session is no longer usable and must be terminated via the task manager.
>> Sometimes the segment violation is trapped by DJGPP's internal fault
>> handler, other times not (caught instead by NT).
> 
> I'd guess these are bugs in the NT DPMI host, but please tell more
> about what programs crashed and what were you doing when they did.

Sounds like maybe if DJGPP's exception handlers catch it, the bug's in
your code, but if you get a *Windows* exception message (dialog, "illegal
operation" blah blah) the bug might be in Windows code...?
My weird video-scribble bug seems to only happen under Windows 95, but not
in pure DOS, which means something in Windows 95 is allergic to some
aspect of my video code, or Allegro's... and when it produces exceptions,
they are Windows dialogs, not DJGPP-esque tracebacks, and lacking in the
important stuff (register dump, stack...)



--
    .*.  Where feelings are concerned, answers are rarely simple [GeneDeWeese]
 -()  <  When I go to the theater, I always go straight to the "bag and mix"
    `*'  bulk candy section...because variety is the spice of life... [me]
Paul Derbyshire ao950 AT freenet DOT carleton DOT ca, http://chat.carleton.ca/~pderbysh

- Raw text -