From: Andy Maddison <maddison AT coventry DOT ac DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: I'm going slightly mad!!
Date: Wed, 25 Feb 1998 10:20:43 +0000
Organization: Coventry University
Lines: 40
Message-ID: <Pine.OSF.3.91.980225100357.6740A-100000-100000-100000@leofric>
References: <199802250048 DOT QAA28497 AT adit DOT ap DOT net> <34F393E9 DOT AEA57781 AT mail DOT coos DOT or DOT us>
NNTP-Posting-Host: leofric.coventry.ac.uk
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <34F393E9.AEA57781@mail.coos.or.us> 
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk


Last night I ported (if that's the right word) my code to compile under 
Borland C++ 4.51 (using the Huge model), and it still terminated at the same 
point.  The message I was given was 'floating point error, stack fault'.
So I can't blame the DJGPP package anymore.  What I will do is run the 
program on some other machines and see what happens.

On a side note:  If I'm using the 'Huge' model in Borland C++, do I have 
to make all my pointers far?, and can I create arrays bigger than 64k?, 
if so how big?. How much memory do I actually have at my disposal?.  Sorry, 
but I don't really understand how memory is used by a program, if 
someone could give a explanantion it would be very helpful. 

> 
> > At 10:45  2/24/1998 +0000, Andy Maddison wrote:
> > >I've been using DJGPP for a while now, just basic C++ 3d graphics
> > >programming, and everything has been going quite well.  But now I've run
> > >into some strange problems:
> > >
> > >When I execute my current piece of work I sometimes get a General
> > >Protection Fault or Floating Point Error, but not everytime!
> > >So why does an unchanged program crash periodically?
> > >
> >  <snip>
> > Weird, irreproducible problems like this are often the sign of some kind of
> > hardware failure. The first thing that comes to mind is bad memory. I'd
> > suggest testing it somehow (maybe someone will follow up and recommend a
> > tester), and replacing it if there is a problem. You might want to back up
> > your data in the meantime.
> 
>   I don't think it is a hardware problem.  I really don't.  Win95 is a strange
> beastie.  I suggest powering your computer off for about 5 minutes, then booting
> into DOS only (hit F8 while it is loading, don't let it go into Win95 at all) and
> then try your programs.  I have that Win95's DPMI server lets you do things that
> you should be able to do.  Maybe if you get it working in a DOS only enviroment
> then you won't have this problem anymore.
> 
> Jason
> 
>>