Date: Tue, 11 Nov 1997 15:52:53 +0100 (GMT+0100)
From: Mrazek Petr <mrazek AT cas3 DOT zlin DOT vutbr DOT cz>
To: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
cc: Konference DJGPP <djgpp AT delorie DOT com>
Subject: Re: Degugging large projects under RHIDE
In-Reply-To: <Pine.LNX.3.95.971111111909.1351A-100000@posaune.hrz.tu-chemnitz.de>
Message-ID: <Pine.LNX.3.91.971111154002.11205A-100000@cas3.zlin.vutbr.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

> > Is there any restrictions in RHIDE?
> 
> The only restrictions (and probably your problem) is the limitation
> of your memory. How much do you have?
> 
> As an example that also larger projects work you can take RHIDE itself.
> The total size of rhide.exe with debug information included is about
> 5 MB and I can debug it without problems (but I have 80MB RAM installed
> :-)
> 
> Robert
I have upgraded my 386DX40 from 8 to 20 MB RAM. You are right, 
debugging is possible now (under DOS). After the start of RHIDE it 
displays 117M/15M of available memory. Is there values for [all available 
including free disk space for swapping]/[available RAM]?
Under OS/2 I cannot debug because RHIDE displays by example 62M/3K (it's 
with 64 MB of DPMI memory for it). This 3K is independent value from DPMI 
memory I give RHIDE (there is always there). And so I cannot debug under 
OS/2.
Have you any experiences with RHIDE under OS/2?

Thanks, Petr Mrazek