🚀 go-pugleaf

IA>In article <1992Aug3.140521.14803@vela.acs.oakland.edu>,
IA>bcmatusz@vela.acs.oakland.edu (Brian Matusz) writes:
IA>>
IA>>In article <1992Aug3.111930.19189@ifi.unizh.ch> erzberg@ifi.unizh.ch (Martin
IA>zberger) writes:
IA>>
IA>>>Can anybody see what's wrong with the following piece of code? I cut it
IA>>>down from a large utility which compiles and runs fine on a SUN.
IA>>>With the IBM C Set/2 compiles, it generates a TRAP. Looking with the
IA>>>debugger, the TRAP gets generated in the initialisation phase (I think
IA>>>at the moment the library gets called to initialize).
IA>>>When I remove any of the two declarations, the program will "run" (of
IA>>>course it does nothing).
IA>>>Now here the code:
IA>>>
IA>>>#include <stdlib.h>
IA>>>
IA>>>main(int argc, char *argv[])
IA>>>{
IA>>>  char     *test1 = NULL;
IA>>>  int       test2[32768];
IA>>>}
IA>>

IA>   Almost certainly insufficient stack space. Local variables reside on
IA>the stack, and the default is quite a bit smaller than 32K. Use
IA>/St:42000 on the link command line, and the program should work.

IA>Regards,
IA>Ian.
Even that won't be enough.  You'll need 128k stack for the integer
array alone.    Probably better to use malloc(), or make test2 global.
---
 . SLMR 2.1a . Eeezz beeg trouble for moose and squirrel!