Path: utzoo!dptcdc!jarvis.csri.toronto.edu!mailrus!ames!elroy!jato!zupke
From: zupke@jato.Jpl.Nasa.Gov (Brian Zupke )
Newsgroups: comp.sys.amiga.tech
Subject: Aztec-C and Stack size
Message-ID: <1137@jato.Jpl.Nasa.Gov>
Date: 18 Apr 89 19:51:12 GMT
Reply-To: zupke@jato.UUCP (Brian Zupke (JPL Amiga Club Pres.))
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 16

>  [suggest problem is local variables] 
>As a test of this problem you can compile with the 
>+m switch which enables stack-checking code to be performed  as part of the 
>function startup sequence.  
>   The description of the +m option is from the manual, but I have not  
>tested it personally.  Let us know if this is the problem and if the +m 
>option performs as advertised! 

    Well, local variables definately caused the crash (I have several large
arrays).  To verify that my local variables were the problem, I made them
much smaller and the program ran fine with a stack size of 4000.  I used 
the +m (interesting that my Aztec-C manual doesn't mention this option!)
option when I compiled  my program but when I ran it, it crashed like it
normally did, so apparently the option doesn't work.    

--Brian