Message-ID: <37D7020E.51427BD5@unb.ca>
From: Endlisnis <s257m AT unb DOT ca>
X-Mailer: Mozilla 4.61 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: WARNING: DOS is about to die
References: <8D53104ECD0CD211AF4000A0C9D60AE30163726C AT probe-2 DOT acclaim-euro DOT net> <37D5D74D DOT 3BB AT earthlink DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 26
Date: Thu, 09 Sep 1999 21:13:01 GMT
NNTP-Posting-Host: 198.164.188.40
X-Trace: news20.bellglobal.com 936911581 198.164.188.40 (Thu, 09 Sep 1999 17:13:01 EDT)
NNTP-Posting-Date: Thu, 09 Sep 1999 17:13:01 EDT
Organization: Sympatico
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Rez wrote:

> Question, then: I beta-test for a coder who works with DJGPP under
> Win95. I test our app exclusively in real       DOS. About half the time when
> there's a bug, the program runs just fine under Win95 in a DOS box (both
> for the coder and my testing partner) but segviols before it even gets
> fully loaded under real DOS with CWSDPMI. Sometimes this happens even
> with trivial bugs, like a wonked menu item. I realise this is vague, but
> anything in particular which causes this dichotomy (bug has no effect
> under Win95, dies spectacularly under DOS) ???  ISTM if we knew what
> sort of things cause this, we (ie. our coder) could avoid 'em up front.

    Dereferencing NULL pointers is NOT caught under Win9x, but IS caught under
cwsdpmi, so > 90% of these types of issues are caused by null-pointer
dereferencing.


--
     (\/) Endlisnis (\/)
          s257m AT unb DOT ca
          Endlisnis AT HotMail DOT com
          ICQ: 32959047