Mail Archives: djgpp/1998/05/03/14:04:34
Al Wong wrote:
>
> > 29K? I seriously hope that's not what you did, because that is far too
> > little for most programs. The default stack size for all DJGPP progs is
> > 256K, but the C++ compiler (and occasionally the linker) may require
>
> Oops! I meant the MINIMUM stack size was set to 29K! That's what it
> was set before using the Borland compiler. I have since increased the
> minimum to 512K! :)
You mean in the program itself or in the stub? The _default_ minstack
for all DJGPP programs is 256K; if yours is 29K then there's something
wrong with your DJGPP installation. In fact, considering the rest of
your reported problems I think you got either the wrong version of DJGPP
or are mixing programs from different incompatible versions. The latest
version of DJGPP is 2.01, and can be found in the subdirectories of
SimTel beginning with 'v2'. Some DJGPP packages in these directories
have multiple versions, so make absolutely sure you not only get the v2
programs, but the latest revisions of the programs.
> > > and the heap size to 40K (using CWSPARAM.EXE):
> >
> > Careful; making the heap size too large wastes conventional memory. If
> > you have any problems running multiple nested programs (make, for
> > example), try reducing this value.
>
> The larger modules wouldn't compile unless I increased the heap size.
That's okay, but 40K is still a bit much. Mine works fine set to 256
paragraphs (10K) and I have a lot more memory than you do.
> The DJGPP FAQ that came in the ZIP file does NOT HAVE a section 6.10
> and 6.12! Is there another FAQ??? I'll have to take a look at the
> on-line FAQ...
Which FAQ that came in which zipfile? The latest version of the DJGPP
FAQ is v2.10 and it comes in v2/faq210b.zip from SimTel. Please
describe in greater detail how you obtained and installed DJGPP, because
it looks like you got either an obsolete or half-crippled version!
> RHIDE shows 3M/2M for virtual/physical memory. Is there a way
> to increase this??? I have a 486 with 8MB of RAM, 1M disk cache.
> I have followed the instructions in the FAQ for machines with
> 5M-8M of RAM but the 486 won't compile the larger modules.
How are you running your programs? If you are running from a Windows
shell, you should increase the available memory for DOS programs. In
Windows 3.1, use the PIF Editor to edit _default.pif and dosprmpt.pif:
increase the maximum memory sizes for conventional, EMS, XMS, and DPMI
to -1 (auto). In Windows 95, open the MS-DOS Prompt properties sheet,
select the Memory tab, and manually set DPMI Memory to 65535K.
From plain DOS, cwsdpmi uses the hard drive to provide swap space, so if
you really are that low on RAM, make sure you have plenty of HD space
free.
> time in parse 0.769230
> time in integration 0.000000
> time in jump 0.109890
> time in cse 0.000000
> time in loop 0.000000
> ...
>
> How do I disable this?
It should be disabled by default already. Make sure you aren't passing
the -Q switch to gcc.
> Yes, I was wondering if the linker also had to be told not to link in the
> debugger (a la borland). I don't intend on using the "-s" until I
> satisfied the program works well enough for release.
As corrected, the '-s' switch should only be used during linking;
stripping the symbols out in the compilation stage will make your object
files useless. :-)
--
---------------------------------------------------------------------
| John M. Aldrich | "Be wary of strong drink. It can |
| aka Fighteer I | make you shoot at tax collectors-- |
| mailto:fighteer AT cs DOT com | and miss." |
| http://www.cs.com/fighteer | - Lazarus Long |
---------------------------------------------------------------------
- Raw text -