🚀 go-pugleaf

In article <1992Aug3.111930.19189@ifi.unizh.ch> erzberg@ifi.unizh.ch (Martin Erzberger) writes:

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

Not knowing for sure, but I'm asuming you're compiling 16-bit code ...
the 32k ints (at two bytes each) are 64k ... which is the size of your
data segment.  Add the pointer and you've overflowed your data segment...
the initialization of the 32768th element of the integer array causes
you to try and access memory you don't own.

Just a guess ...
Brad Wilson (via a friend's account)