From: Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Compiled RHIDE 1.4 works in Win95, but not in DOS?!
Date: Tue, 27 Jan 1998 08:47:15 +0100
Organization: University of Ghent, Belgium
Lines: 37
Message-ID: <34CD9103.7A93@rug.ac.be>
References: <199801170037 DOT QAA07214 AT adit DOT ap DOT net>
NNTP-Posting-Host: eduserv1.rug.ac.be
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
CC: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Nate Eldredge wrote:
> 
> At 06:36  1/15/1998 -0800, Curtis Wensley wrote:
> >Okay.  This is my predicament:
> >I have successfully compiled RHIDE with absolutely no errors or warnings
> >whatsoever.
...

> >Anyway, i tried to run the compiled EXE (2mb until i stripped all the
> >useless stuff from the exe) in DOS, and it would give (repeadedly) an error.
> >I cannot give you the error information, because my computer is literally
> >frozen while it continuously writes out the same error information.
> Literally frozen? Really. Have you chipped the ice off yet? :)
> Seriously though, can you give any idea of what the message was like?
> Obviously other people have had RHIDE work so they can't reproduce your problem.

Most people don't recompile RHIDE themselves though.

I'd like to second this. The IDEGC.EXE runs perfectly (I think) in W95
and does what Wensley describes in DOS:
Page faults occur continuously; considering the core dump info ;), more
in particular the value in ESP, they probably occur recursively from
within the routine that produces the trace-back.

The precompiled RHIDE.EXE runs perfectly, euh..., well, almost
perfectly.

IIRC I was able to recover my session by CTRL+C.

I used djdev201, gdb416s, rhide14s and the right tv as source code.

Bye.

-- 
 \ Vik /-_-_-_-_-_-_/   
  \___/ Heyndrickx /          
   \ /-_-_-_-_-_-_/