From: ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE problem...
Date: 3 Aug 1997 05:20:08 GMT
Organization: The National Capital FreeNet
Lines: 27
Message-ID: <5s14e8$sit@freenet-news.carleton.ca>
References: <01bc9e14$098e8180$854c8bc0 AT Emir DOT usask DOT ca>
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
Precedence: bulk


"Emir H." (emh076 AT mail DOT usask DOT ca) writes:
> 	
> Is there any known reason why does RHIDE sometimes reset the system under
> Win95, and sometimes makes illegal instruction or general fault ?

Ditto. It only happens when running a program in RHIDE's internal
debugger, then hitting ctrl-break or ^C. It just hangs, and if you hit a
bunch more ^C it dies with a GPF in Windows. It is supposed to say
"Exiting due to signal SIGINT..." in a Message Window and point your source
screens at the line where it was executing when you killed it, not crash.
RHIDE 1.1 worked fine; but I began to observe the problem immediately
after updating to 1.3.

Also, is there anything that could cause a program to crash a Windows DOS
prompt from the prompt, cause a SIGSEGV in stricmp() in GDB, and in RHIDE
cause a message "Program has received signal SIGABRT" without any error
message, call frame traceback EIPs or nothing?
(At least I know where my only call to stricmp() is. Too bad I have no
clue how that pointer is getting f*cked up, since it is set up correctly
by the damned constructor...)

--
    .*.  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