From: ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE 1.1 Crash
Date: 20 Feb 1997 04:06:56 GMT
Organization: The National Capital FreeNet
Lines: 43
Message-ID: <5egil0$d9g@freenet-news.carleton.ca>
References: <330a380a DOT 18093054 AT news DOT why DOT net>
Reply-To: ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
NNTP-Posting-Host: freenet3.carleton.ca
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp


Sed (sdarl AT why DOT net) writes:
> 	Hello all,
> 
>   Using RHIDE 1.1 when I trace through a program, and it comes to this
> function below, RHIDE closes down, and returns to the operating
> system. 
>  --When I normal run the program that contains this function, all goes
> well.--
>   Also, if I set a breakpoint somewhere in the middle of the function,
> I can then step through it. Using unix based C compilers, I can trace
> through normally, so I'm led to believe this is an RHIDE/DPMI server
> issue. The shutdown happens upon entry to the function. The first
> command in the function is not even executed. The function is also
> called by main.
> 
>  The system I am using is a Pentitum 75 with 24 megs running Win95. I
> have a Stealth 64 1Meg SE graphics card. My autoexec.bat and
> config.sys contain nothing out of the ordinary, except a NOEMS switch
> on EMM386. I run Rhide from inside Win95 under full screen Dos window.
> Djgpp is installed and 100% operational otherwise.
> 
>  When RHIDE stops, it just disappears. The temp files are still in
> place though, but RHIDE returns straight to Win95 which may mean that
> Win95 is preempting a bad call.
> 
>  I was wondering if anyone else experienced this situation, and how it
> may have been overcome. Since I don't have immediate access to another
> DPMI server, I was wondering if it may be Win95 DPMI server.

Try booting with F8, going to command prompt only, and running rhide and
duplicating the crash.

* If it was Win 95 pre-empting something it now will not happen
* If it was a crash with a stack trace and stuff, such as the dreaded
  SIGSEGV, you'll actually get to see the stack trace instead of the window
  closing and erasing it in a millisecond.

--
    .*.  Where feelings are concerned, answers are rarely simple [GeneDeWeese]
 -()  <  When I go to the theater, I always go straight to the "bag and mix"
    `*'  bulk candy section...because variety is the spice of life... [me]
Paul Derbyshire ao950 AT freenet DOT carleton DOT ca, http://chat.carleton.ca/~pderbysh