From: "Richard L.F. van Paasen" <R DOT L DOT F DOT v DOT Paasen AT stud DOT tue DOT nl>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Infinite number of protection faults
Date: Mon, 30 Sep 1996 23:16:57 -0700
Organization: University of Technology Eindhoven
Lines: 34
Message-ID: <3250B759.278E@stud.tue.nl>
References: <324F0DA9 DOT 238C AT stud DOT tue DOT nl> <324FE68D DOT 61AC AT jk DOT uni-linz DOT ac DOT at>
Reply-To: R DOT L DOT F DOT v DOT Paasen AT stud DOT tue DOT nl
NNTP-Posting-Host: annex1s20.urc.tue.nl
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

Roland Exler wrote:
> 
> Richard L.F. van Paasen wrote:
> >
> > SUBJECT: infinite number of protection faults
> 
>   < parts of the message deleted >
> 
> > And so on, the general protection fault seems to appear in an
> > infinite loop. The only way to stop it is to reboot my computer!
> > Note the growing "call frame traceback EIPs", the last one is
> > repeated infinitely.
> 
> I've a similar problem with a program created with djgpp, which depends on the
> data processed in my case. I had not enough time to trace down the problem, as
> debugging is very time-consuming if you've to reboot after each run.
> 
> If I know more about my problem, I'll post it.
> 
> Roland
> 

I've found that I the infinite loop of protection faults was due to a
strange
situation: I have a library of my own that has some object file
duplicated
(i.e. in librvp.a the module init.o appeared three times). The linker
took the first one, which was slightly different from the newest init.o
Removing the library and building it again, and finally rebuiding my
project did solve the inifinite protection faults. Although...there was
one
GPE left, but that's Ok (debuggable :_)

Richard van Paasen.