From: Eric Rudd <rudd AT cyberoptics DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RMCB bomb
Date: 9 Mar 1997 03:45:16 GMT
Organization: CyberOptics Corp
Lines: 44
Message-ID: <5ftboc$3oj@hagar.cyberoptics.com>
NNTP-Posting-Host: rudd.cyberoptics.com
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

>>On 3 Mar 1997, Eric Rudd wrote:
>
>> I am running DJGPP v2.01 on a Pentium 90 computer with 32 MB of RAM, IBM
>> PC-DOS 6.30, HIMEM.SYS, the Norton Cache, v6.01, but no EMM386, QEMM, or
>> Windows.
>> 
>> Every few days, the compiler crashes for no apparent reason.  The last
>> time it crashed I transcribed the dump:
>
>and Eli Zaretskii replied:

>Try to unload Norton Cache and use Smartdrv instead.  It's a bit slower, 
>but Norton Cache is known to make trouble in some cases.  If the problem 
>disappears, you will know that the cache is the cause.

I switched over to SMARTDRV, and all was well for a few days.  But today I
was compiling intensively, and I had two "RMCB" hangs.  One produced the
message

Page fault cr2=740062f8 in RMCB at eip=b181; flags=3056
eax=1 ebx=00000000 ecx=00000000 edx=00000007 esi=00001a65 edi=000030d8
ebp=0005e9a0 esp=000030bc cs=a7 ds=3b es=33 fs=33 gs=bf ss=33 error=0004
Page fault cr2=75010000 in RMCB at eip=b181; flags=3056
eax=1 ebx=00000000 ecx=00000000 edx=00000007 esi=00001a65 edi=000030d8
ebp=0005e9a0 esp=000030bc cs=a7 ds=3b es=33 fs=33 gs=bf ss=33 error=0004

Also, I had one similar hang at work, where I'm running SMARTDRV and QEMM
v7.0.  The one common thread in all these bombs has been DJGPP v2.01, so
I'm suspecting it more than before.

It still seems to have something to do with typing ahead during a
compilation.  Is this an inherent problem with running protected-mode apps
while real-mode interrupts are occurring?  I suppose I could just stop
typing ahead, but that would be like visiting a doctor with the complaint,
"Doctor, it hurts when I do this," only to be told "Well, don't do that!"
;-)

I would be happy to gather additional data, but I don't feel at all
qualified to fix the problem.  I would appreciate any help anyone could
give me.  Has anyone else been having problems of this nature?

-Eric Rudd
rudd AT cyberoptics DOT com