From: "A. Sinan Unur" <asu1 AT cornell DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: a few questions...
Date: Fri, 12 Sep 1997 12:44:05 -0500
Organization: Cornell University
Lines: 18
Sender: asu1 AT cornell DOT edu (Verified)
Message-ID: <34197F65.23F2@cornell.edu>
References: <5v87rt$2j4$1 AT kurica DOT wt DOT com DOT au>
	 <0Zxy$AA7IBG0EwOE AT jenkinsdavid DOT demon DOT co DOT uk>
	 <3418FCCA DOT 4166984E AT Mathematik DOT TU-Chemnitz DOT DE>
	 <341906A1 DOT 590A8F09 AT Mathematik DOT TU-Chemnitz DOT DE> <34192421 DOT 7544 AT cornell DOT edu> <JLodrCAf1TG0EwIC AT jenkinsdavid DOT demon DOT co DOT uk>
Reply-To: asu1 AT cornell DOT edu
NNTP-Posting-Host: 128
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

David Jenkins wrote:

> 
> So, why does Dos handle catch SIGSEGV errors and Win95 doesn't??
> Is Win95 just ignoring them to avoid crashes or something??
> 

it is not DOS, rather CWSDPMI that creates the exception. i do not know
enough about the technical details to explain it very well. my policy is
to always boot to plain dos (not ms-dos mode) and test my programs there
once in a while (after all, it is convenient to work in windows.)
anyway, if your program crashes under cwsdpmi but seems to run fine in a
dos box, that means, in all likelihood, that there is a pointer related
bug in your code.

have fun.

  -- Sinan